Skip to content

Fix HTTP/3 behavior in case of client reset. #13179

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

Open
wants to merge 4 commits into
base: jetty-12.1.x
Choose a base branch
from

Conversation

sbordet
Copy link
Contributor

@sbordet sbordet commented May 28, 2025

The test case verifies that if the demand callback is invoked, then the failure listener is not invoked, but it was failing with HTTP/3.

The test case verifies that if the demand callback is invoked, then the failure listener is not invoked, but it was failing with HTTP/3.

Signed-off-by: Simone Bordet <[email protected]>
Signed-off-by: Simone Bordet <[email protected]>
Copy link
Contributor

@lorban lorban left a comment

Choose a reason for hiding this comment

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

I think the fix looks good, and the two TODOs should be left for another PR.

@sbordet sbordet marked this pull request as ready for review May 28, 2025 15:27
@sbordet sbordet changed the title WIP to fix HTTP/3 behavior in case of client reset. Fix HTTP/3 behavior in case of client reset. May 29, 2025
@lorban
Copy link
Contributor

lorban commented May 30, 2025

Build 4 failed because of EE11's JSP dependency, which is unrelated to this PR. Hopefully a merge of 12.1.x would solve that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

2 participants