You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhancement Description
The existing PathMappingsHandler does not record the matched PathSpec that lead to the decision to call the specific handler.
I propose we add the matched PathSpec to the Request attributes before calling the matched Handler.
This has 2 benefits.
The PathSpec details (like regex matched groupings, and uri-template variables / path-params, path-info, etc) can be obtained.
The Request.getPathInContext(Request) can participate in the smart resolution of path-in-context from the matched PathSpec (as a primary source if a ContextHandler is not present?)
The text was updated successfully, but these errors were encountered:
joakime
changed the title
PathMappingsHandler records matched PathSpec in Request Attributes
PathMappingsHandler exposes PathSpec and Context based on PathSpec
Mar 7, 2024
Jetty version(s)
12.0.7
Enhancement Description
The existing
PathMappingsHandler
does not record the matchedPathSpec
that lead to the decision to call the specific handler.I propose we add the matched
PathSpec
to the Request attributes before calling the matchedHandler
.This has 2 benefits.
PathSpec
details (like regex matched groupings, and uri-template variables / path-params, path-info, etc) can be obtained.Request.getPathInContext(Request)
can participate in the smart resolution of path-in-context from the matchedPathSpec
(as a primary source if aContextHandler
is not present?)The text was updated successfully, but these errors were encountered: