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
Make a HEAD or GET request using curl:
curl -I -H "transfer-encoding: chunked" url_to_yaws_server
which should tie up an acceptor for minutes. Start a few more such requests to tie up all acceptors.
The text was updated successfully, but these errors were encountered:
I'll look into it. It's likely that some streaming process needs a timeout.
Sorry, something went wrong.
Replace transfer-encoding with content-length to get a similar issue. Post data with mismatching content-length also ties up an acceptor.
transfer-encoding
content-length
curl -H "content-length: 5" --data "abc" URL_YAWS_SERVER
There is also the case of a slow client for example one that connects and then sends one byte every 10 seconds (See Slowloris).
All these code paths eventually reach yaws:cli_recv/3 which do a recv on the socket with a default timeout #gconf.keepalive_timeout.
yaws:cli_recv/3
#gconf.keepalive_timeout
nginx seems to handle these cases safely and sensibly.
No branches or pull requests
Make a HEAD or GET request using curl:
which should tie up an acceptor for minutes. Start a few more such requests to tie up all acceptors.
The text was updated successfully, but these errors were encountered: