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
I tried to do this as part of #31547 but reverted the endpoint specific changes because the changes were bigger than expected. The handler mappings support both path pattern and string based matching with path pattern used by the auto-configuration. In case of String-based matching, trailing slashes are supported but that does not seem to be the case with pattern based matching. As part of this issue, we need to do the following:
Drop support for String based matching for actuator endpoints
Consider whether to support trailing slash for actuator endpoints with pattern matching
AbstractWebMvcEndpointHandlerMapping no longer needs to be a MatchableHandlerMapping (this was added to support Spring Security's MvcRequestMatcher but it can do that now without it being a MatchableHandlerMapping).
The text was updated successfully, but these errors were encountered:
There may be some overlap between this issue and #31604.
wilkinsona
changed the title
Consider dropping support for String path matching for MVC endpoint handler mappings
Drop support for String path matching for MVC endpoint handler mappings
Jul 13, 2022
I tried to do this as part of #31547 but reverted the endpoint specific changes because the changes were bigger than expected. The handler mappings support both path pattern and string based matching with path pattern used by the auto-configuration. In case of String-based matching, trailing slashes are supported but that does not seem to be the case with pattern based matching. As part of this issue, we need to do the following:
AbstractWebMvcEndpointHandlerMapping
no longer needs to be aMatchableHandlerMapping
(this was added to support Spring Security'sMvcRequestMatcher
but it can do that now without it being aMatchableHandlerMapping
).The text was updated successfully, but these errors were encountered: