Disable async context timeout when ResourceServlet is serving files asynchronously
#13929
+360
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sbordet
requested changes
Oct 29, 2025
Contributor
sbordet
left a comment
sbordet
left a comment
There was a problem hiding this comment.
Just a better comment in the test.
Please change it also in ee10.
...e11/jetty-ee11-servlet/src/test/java/org/eclipse/jetty/ee11/servlet/ResourceServletTest.java
Outdated
Show resolved
Hide resolved
sbordet
approved these changes
Oct 30, 2025
Signed-off-by: Ludovic Orban <[email protected]>
lorban
force-pushed
the
fix/12.1.x/13922-ResourceServlet-AsyncContext-timeout
branch
from
f80ff7c to
cca3309
Compare
…922-ResourceServlet-AsyncContext-timeout
lorban
deleted the
fix/12.1.x/13922-ResourceServlet-AsyncContext-timeout
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #13922
Note: those are the only (non-test) code places I found where the async context timeout isn't explicitly set.