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
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.
Uh oh!
There was an error while loading. Please reload this page.
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:
The text was updated successfully, but these errors were encountered: