Ok, so it doesn't have anything to do with the AP/Client thing, but is literally just a client request when a server is open?
It's taken me a while to find it, but it looks like it's to do with the ESP8266 AT command driver. Basically it does the GET request and everything's fine, but then it gets a socket closed command. At that point the socket is closed but there's still data, and the server thinks that means that a socket has opened - so part of the GET gets treated as another request to the server.
So yeah, it is something broken in Espruino. I'll see if I can find a nice fix for it
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.
Ok, so it doesn't have anything to do with the AP/Client thing, but is literally just a client request when a server is open?
It's taken me a while to find it, but it looks like it's to do with the ESP8266 AT command driver. Basically it does the GET request and everything's fine, but then it gets a socket closed command. At that point the socket is closed but there's still data, and the server thinks that means that a socket has opened - so part of the GET gets treated as another request to the server.
So yeah, it is something broken in Espruino. I'll see if I can find a nice fix for it