Skip to content

Review path matching options and defaults in the new path matching algorithms [SPR-14993] #19559

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

Closed
spring-projects-issues opened this issue Dec 7, 2016 · 1 comment
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Dec 7, 2016

Rob Winch opened SPR-14993 and commented

We should review options and defaults we would like to have as part of the new path matching refinements work under #19112. Especially on the reactive side we can choose different defaults and there be an opportunity to do that for existing code if the switch (from AntPathMatcher to the new one) is explicit.

For example, does the pattern /foo match /foo, /foo/, /foo.html, / foo.

As part of this we should also consider default options for the strategy for determining what the path that is being matched on is, i.e. HttpRequestPathHelper in terms of normalizing the path by removing .., ., path parameters (i.e. semi-colon content), etc.


Issue Links:

@spring-projects-issues
Copy link
Collaborator Author

spring-projects-issues commented Jun 12, 2017

Brian Clozel commented

This has been resolved by the related issues linked in this one.

Quick summary of those changes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants