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
09:45:50.595 [http-nio-8080-exec-1] INFO o.s.web.servlet.DispatcherServlet - Initializing Servlet 'dispatcherServlet'
09:45:50.596 [http-nio-8080-exec-1] INFO o.s.web.servlet.DispatcherServlet - Completed initialization in 1 ms
{GET [/*/vehicle/vehiclesByManufacturer** || /*/vehicle/vehiclesByManufacturer/**]}
java.lang.IllegalArgumentException: Expected parsed RequestPath in request attribute "org.springframework.web.util.ServletRequestPathUtils.PATH".
at org.springframework.util.Assert.notNull(Assert.java:201)
at org.springframework.web.util.ServletRequestPathUtils.getParsedRequestPath(ServletRequestPathUtils.java:77)
at org.springframework.web.servlet.mvc.condition.PathPatternsRequestCondition.getMatchingCondition(PathPatternsRequestCondition.java:192)
at org.springframework.web.servlet.mvc.method.RequestMappingInfo.getMatchingCondition(RequestMappingInfo.java:399)
at org.springframework.web.servlet.mvc.method.RequestMappingInfo.getMatchingCondition(RequestMappingInfo.java:66)
...
I may be mistaken but I don't think this is completely fixed for all possible paths. (It also threw an error when path was "{ [/error]}" as well)
The path you see "{GET [//vehicle/vehiclesByManufacturer** || //vehicle/vehiclesByManufacturer/**]}" is represented in the controller as @RequestMapping(value = ["/vehiclesByManufacturer**","/vehiclesByManufacturer/**"], method = RequestMethod.GET)
This allows for multiple URI's to be handled by one endpoint or for an endpoint to have an ALIAS and is covered in documentation.
I believe this may not be being considered for the pathing as it is throwing an error???
The text was updated successfully, but these errors were encountered:
Where is that code written and called?
If this is done outside of the Spring Boot or Spring Framework codebases (for example, a custom filter), this might be a duplicate of #28874.
That's definitely a duplicate of #28874.
You custom filter is not initializing the request path. Note the comments in that linked issue saying that this is not an approach that the team supports.
Thanks!
I have a method that is reading the mapping info in order to work with/validate api connectors
This throws an identical error to #24877
I may be mistaken but I don't think this is completely fixed for all possible paths. (It also threw an error when path was "{ [/error]}" as well)
The path you see "{GET [//vehicle/vehiclesByManufacturer** || //vehicle/vehiclesByManufacturer/**]}" is represented in the controller as
@RequestMapping(value = ["/vehiclesByManufacturer**","/vehiclesByManufacturer/**"], method = RequestMethod.GET)
This allows for multiple URI's to be handled by one endpoint or for an endpoint to have an ALIAS and is covered in documentation.
I believe this may not be being considered for the pathing as it is throwing an error???
The text was updated successfully, but these errors were encountered: