Warn about unsupported "/path/**/other" patterns with WebFlux PathPatternParser #24958
Comments
bclozel
added a commit
that referenced
this issue
May 11, 2020
Prior to this commit, patterns like `"/path/**/other"` would be treated as `"/path/*/other"` (single wildcard, i.e. matching zero to many chars within a path segment). This will not match multiple segments, as expected by `AntPathMatcher` users or by `PathPatternParser` users when in patterns like `"/resource/**"`. This commit now rejects patterns like `"/path/**/other"` as invalid. This behavior was previously warned against since gh-24958. Closes gh-24952
kenny5he
pushed a commit
to kenny5he/spring-framework
that referenced
this issue
Jun 21, 2020
Prior to this commit, patterns like `"/path/**/other"` would be treated as `"/path/*/other"` (single wildcard, i.e. matching zero to many chars within a path segment). This will not match multiple segments, as expected by `AntPathMatcher` users or by `PathPatternParser` users when in patterns like `"/resource/**"`. This commit now rejects patterns like `"/path/**/other"` as invalid. This behavior was previously warned against since spring-projectsgh-24958. Closes spring-projectsgh-24952
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is an early warning of behavior changes coming with #24952 in 5.3.0.
When applications use
PathPatternParserto parse patterns with"**"in the middle, we should log a WARNING log message about this particular pattern saying that it will be processed as a"*"and rejected in the future.We should also improve the Javadoc and reference documentation to better explain the cases supported here.
The text was updated successfully, but these errors were encountered: