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

Fixes #12249 - HTTP/2 responses with Content-Length may have no content. #12250

Merged

Conversation

sbordet
Copy link
Contributor

@sbordet sbordet commented Sep 8, 2024

Fixed HttpReceiverOverHTTP2.read() to return a failed chunk if the stream has been reset.

This closes the window where a RST_STREAM frame may be received, drain the DATA frames in HTTP2Stream, and the application reading exactly at that point.

Fixed HttpReceiverOverHTTP2.read() to return a failed chunk if the stream has been reset.
This closes the window where a RST_STREAM frame may be received, drain the DATA frames in HTTP2Stream, and the application reading exactly at that point.

Signed-off-by: Simone Bordet <[email protected]>
@sbordet sbordet requested review from lorban and gregw September 8, 2024 17:31
@sbordet sbordet linked an issue Sep 8, 2024 that may be closed by this pull request
Signed-off-by: Simone Bordet <[email protected]>
@sbordet sbordet requested a review from lorban September 9, 2024 13:54
@sbordet sbordet merged commit fa0502d into jetty-12.0.x Sep 9, 2024
8 of 10 checks passed
@sbordet sbordet deleted the fix/jetty-12.0.x/12249/h2-drained-response-content branch September 9, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

HTTP/2 responses with Content-Length may have no content
2 participants