You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 18, 2019. It is now read-only.
We discovered that when we are using nodejs >= 6.0 sockets are left open when a http parsing error occurs during a request. This issues didn't occur in nodejs 4.
To reproduce this error just set up a minimal hapi server and curl it with an invalid request:
Hi,
We discovered that when we are using nodejs >= 6.0 sockets are left open when a http parsing error occurs during a request. This issues didn't occur in nodejs 4.
To reproduce this error just set up a minimal hapi server and curl it with an invalid request:
Start the server with debug enabled:
NODE_DEBUG=http node index.js
Now query it with an request containing for example a white space:
curl -G "localhost:3000/white space"
The result is, that the socket is not closed and the request hangs until the timeout is reached:
Expected behavior would be that the socket is closed right after the request. This is the case when using only http, express or hapi with nodejs 4:
The text was updated successfully, but these errors were encountered: