"Received incoming connection" without request for large request

[Kexkey]

Hi! I'm facing a problem with large requests on info/. I can't reproduce on your server, but it happens on the servers I installed opentimestamps.org on. Maybe you can help?

It's not the same as #21. I tried to strip down the more I could by not installing anything else than this repo. So no SSL, no nginx reverse proxy, nothing else than the gulp-connect that is listening on default port 8080. You can try it with Firefox with this request: https://gist.github.com/Kexkey/a11fd2f111e96b24e197f8928e69a5e9

With curl (https://gist.github.com/Kexkey/2a86514252a958950c2ddcff0589fb9d), I am getting a 400 at each request when I provide the same headers Firefox does to have a long enough request (8242 bytes). With Firefox, it's different on each refresh, sometimes everything is there and other times there are multiple errors 400 on the requests (see the Network tab). Here is a screenshot when partial response:

I added debug: true in the gulpfile to see what's going on. When the error occurs, we can see the incoming connection without the request. When the error doesn't occur, we can see the incoming connection followed by the incoming request.

(here, for example, is the console of the previous screenshot. I got 4 errors 400 and one that went through -- the 400 is not always on the same file, sometimes it's on the main /info/? request meaning there's no other requests made and a blank page, obviously)

[17:17:11] Received incoming connection from 172.x.0.y
[17:17:13] Received incoming connection from 172.x.0.y
[17:17:13] Received request GET /info/?004f70656e54696d6573...960d73d7190103a8bb22
[17:17:13] Received incoming connection from 172.x.0.y
[17:17:13] Received incoming connection from 172.x.0.y
[17:17:13] Received incoming connection from 172.x.0.y

Everything works fine with smaller requests.

I don't know if it's the version of nodejs, npm, gulp, gulp-connect or else that got installed when running npm install. What versions are you running on your server? Strange, it always works well on opentimestamps.org.

Thanks!

[Kexkey]

FYI, I replaced gulp-connect (as the HTTP server) by nginx and all is good now.