-
Notifications
You must be signed in to change notification settings - Fork 41.1k
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
EndpointRequest.toLinks() does not match when management.endpoints.web.base-path is '/' #34834
Comments
Can this be worked? or is a triage still planned? WebEndpointProperties ln 70 needs fixing. |
@somayaj You're welcome to work on the issue, I'll assign it to you. Ideally we'll be looking to add a test as well. |
This is deceptively complicated as |
@wilkinsona not sure if this would make sense or would be in the right direction?
|
I am using a different management port with
management.server.base-path: '/management'
andmanagement.endpoints.web.base-path: '/'
.When setting up security as
.requestMatchers(EndpointRequest.toLinks()).permitAll()
, then performing a request over'/management/'
, returns 403Root cause:
WebEndpointProperties.setBasePath
cleans'/'
as''
.Later on, upon first
'/'
call,LinksRequestMatcher
sees the empty basepath and returnsEndpointRequest.EMPTY_MATCHER
, which always evaluates to falseThe text was updated successfully, but these errors were encountered: