-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Jetty-12 EE10 handling of %2F as Alias #8462
Comments
The new behaviour of servlet 6.0 allows a servletPath and/or pathInfo to contain a %2F as an encoded For example, a request to
So this has been resolved incorrectly. Either the path should be for the (probably) non-existent |
This is a provisional workaround for #8462 that fixes the bugs in URIUtil that were preventing encoded %2F being seen as an alias. However, the better ultimate fix would be to see an encoded request as a request for a path segment that includes %2F.
Commit edba0c3 "fixes" this issue by fixing a big in URIUtil that prevented the resource from being seen as an alias. |
Commit edba0c3 broke the |
…t-2f Issue #8462 - Jetty 12 - Adding testcase to prove out "%2F" access behavior in ee10 mode
Closing, as we have plenty of test cases for this now in Jetty-12 |
Jetty version(s)
jetty-12 ee10
Description
The
org.eclipse.jetty.ee10.webapp.WebAppContextTest#testProtectedTarget
has some important use-cases commented out with regards to handling of %2FThe text was updated successfully, but these errors were encountered: