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
We have in hyper a HTTP1 header read timeout (which is strangely not available for HTTP?) and this works great... if the client sends at least one byte (or a newline?).
If the client never sends a single byte, and just holds the connection open, the timeout never triggers.
I suggest we either make the timeout trigger even when no bytes have been sent (make the timer start ticking the minute serve_connection() is called) or we introduce another field explicitly for first byte timeout.
This will harden hyper servers against clients who attempt to open and hog connections open without any intention of sending any data.
The text was updated successfully, but these errors were encountered:
We have in hyper a HTTP1 header read timeout (which is strangely not available for HTTP?) and this works great... if the client sends at least one byte (or a newline?).
If the client never sends a single byte, and just holds the connection open, the timeout never triggers.
I suggest we either make the timeout trigger even when no bytes have been sent (make the timer start ticking the minute
serve_connection()
is called) or we introduce another field explicitly for first byte timeout.This will harden hyper servers against clients who attempt to open and hog connections open without any intention of sending any data.
The text was updated successfully, but these errors were encountered: