-
• #2
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 -
• #4
fixed, it'll be in 2v02
While working with the Wiznet adapter on an Espruino Original Board (well, my clone of it), I noticed that there seemed to be a very low cap on the number of requests that can be serviced by it. After making a few requests, it would simply refuse the connection. But try again a minute or two later, and it would work.
I think this is due to browsers trying to keep the socket open (keep alive) - it seemed to be markedly improved - possibly solved - by adding Connection: close to the http headers. Has anyone else noticed/investigated this issue? Is my diagnosis correct? If so, should it be added to the documentation?