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
There is a race condition between client and server. Client could still try to use already closed connection. It results in ugly error "No message received" or similar and retries. That could be disturbing and looks trashy. We saw that with s3. To avoid that case server could send 408 even to the idle connection right before closing it. Mozila does that, the link from it.
That race condition could be severe problem in case of max_keep_alive_requests. For example client does not honor it and keeps sending requests. At max_keep_alive_requests+1 request client receives an error.
Lets consider to implement this approach to close connection gracefully?
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408
There is a race condition between client and server. Client could still try to use already closed connection. It results in ugly error "No message received" or similar and retries. That could be disturbing and looks trashy. We saw that with s3. To avoid that case server could send 408 even to the idle connection right before closing it. Mozila does that, the link from it.
That race condition could be severe problem in case of
max_keep_alive_requests
. For example client does not honor it and keeps sending requests. Atmax_keep_alive_requests+1
request client receives an error.max_keep_alive_requests
introduced in #61793 (comment)_The text was updated successfully, but these errors were encountered: