Skip to content
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

Start http1 header read timeout even when 0 bytes are read #3305

Merged
merged 2 commits into from
Jun 3, 2024

Conversation

jeromegn
Copy link

@jeromegn jeromegn commented Sep 5, 2023

As mentioned in #2675 (comment), the timeout didn't apply if no bytes were written yet.

This moves the start of the timeout's polling before the check for an empty buffer.

@seanmonstar
Copy link
Member

FWIW, this sounds very similar to this other PR, which I paused because of the follow comment: #3185 (comment).

Copy link
Member

@seanmonstar seanmonstar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, this is much wiser. If browsers cannot handle this with preconnects, they should stop looking like bad actors.

@seanmonstar seanmonstar merged commit b5c2592 into hyperium:0.14.x Jun 3, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants