We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is anyone else seeing the situation where Crow does not close the socket of a request until 5 seconds after resp.end() is called?
resp.end()
This is causing an issue with lighttpd proxying for me, where it will not send the next request until 5 seconds after the first one completes.
lighttpd
Wondering if anyone has found a workaround for this.
Thanks.
The text was updated successfully, but these errors were encountered:
may be resolve your problem with #294
Sorry, something went wrong.
No branches or pull requests
Is anyone else seeing the situation where Crow does not close the socket of a request until 5 seconds after
resp.end()
is called?This is causing an issue with
lighttpd
proxying for me, where it will not send the next request until 5 seconds after the first one completes.Wondering if anyone has found a workaround for this.
Thanks.
The text was updated successfully, but these errors were encountered: