You are reading a single comment by @samppa and its replies.
Click here to read the full conversation.
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.
@samppa
@Gordon Unfortunately no help or different behavior in this case.
The 60 second timeout helps to give Espruino time to answer if several requests are buffered to be handled. The server already responds with Connection:close header, but that does not help when the request is not completed properly.
Yes indeed the situation is like a DOS attack, but it should recover after the spam is over and that is not the case at the moment.
Next I will try the wifi disconnect trick. But how the server knows when to do that since everything seems fine on that side?