-
Notifications
You must be signed in to change notification settings - Fork 59
connection pool tries to reuse closed connections #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm getting a similar error, but instead of throwing ErrorReset or ErrorClosed, we just get the underlying socket error. The client has sent a PUT request to the server. Here's the client log from the point where we get the response, and then try to send the next PUT request:
The important thing to notice here is that the server is responding with |
BTW, that's with HTTP-4000.2.5 |
This issue also seems to be the cause of bug in cabal-install which crashes (for me) when using a proxy. |
Fix #14: connection pool tries to reuse closed connections
If a webserver doesn't implement keep-alive (e.g. httpd-shed as currently used in the test harness), HTTP doesn't notice and still tries to send a second request on the same connection.
The text was updated successfully, but these errors were encountered: