I think what's happened is that Espruino's HTTP stuff now reports back HTTP/1.1 instead of HTTP/1.0 and I think that means the default state for the connection is not to automatically close it when before it worked fine?
We should maybe update the examples - however, @MaBe is it worth making Espruino automatically insert a Connection: close header when responding to a request? That might solve a lot of unexpected issues
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Ahh - yes, that sounds about right. Do you have a link to the code you're using? It's just a standard HTTP server like http://www.espruino.com/Internet#server?
I think what's happened is that Espruino's HTTP stuff now reports back
HTTP/1.1
instead ofHTTP/1.0
and I think that means the default state for the connection is not to automatically close it when before it worked fine?@MaBe mentioned something similar here for ESP8266 so I don't think it's WIZnet related: http://forum.espruino.com/conversations/329000/#14551636
We should maybe update the examples - however, @MaBe is it worth making Espruino automatically insert a
Connection: close
header when responding to a request? That might solve a lot of unexpected issues