Skip to content

PathPatternRequestMatcher Include Optional Servlet Path in the pattern #16765

Closed
@rwinch

Description

@rwinch

I wonder if it would be better to change PathPatternRequestMatcher to include the servlet in the PathPattern that should be used instead of having a separate RequestMatcher for the servlet.

Then instead of using pathWithinApplication() it would be the entire PathContainer.

NOTE: Further investigation might be necessary, but this seems like it doesn't work since the contextPath is considered unless pathWithinApplication is used. I'm wondering why framework doesn't allow only ignoring the contextPath.

Metadata

Metadata

Assignees

Labels

in: webAn issue in web modules (web, webmvc)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions