Allow null resource base in ResourceFileServlet with Jetty 12 #334
Conversation
This file contains 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
Signed-off-by: Lachlan Roberts <[email protected]>
|
Gemini encountered an error creating the summary. You can try again by commenting |
maigovannon
approved these changes
Jan 24, 2025
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.
In
com.google.apphosting.runtime.jetty9.ResourceFileServletwe were able to have a nullresourceBasein the case thatcontext.getResource(URIUtil.SLASH + appVersion.getPublicRoot())returned null.However in Jetty 12 the
ResourceFactory#newResourcemethod will throw IAE if the given URL is null.This PR restores the same behavior by allowing
ResourceFileServletto have a nullresourceBasefor the Jetty 12 based runtimes.