Direct matches by URL path work again
This commit fixes a recent regression as a result of 5225a57411
with the determination of non-pattern vs pattern URLs. That in turn affects the ability to perform
direct matches by URL path.
There is also a fix in PathPattern to recognize "catch-all" patterns as pattern syntax.
See gh-24945
This commit is contained in:
@@ -54,8 +54,8 @@ public class PathPatternTests {
|
||||
public void hasPatternSyntax() {
|
||||
PathPatternParser parser = new PathPatternParser();
|
||||
assertThat(parser.parse("/foo/*").hasPatternSyntax()).isTrue();
|
||||
assertThat(parser.parse("/foo/**").hasPatternSyntax()).isFalse();
|
||||
assertThat(parser.parse("/foo/{*elem}").hasPatternSyntax()).isFalse();
|
||||
assertThat(parser.parse("/foo/**").hasPatternSyntax()).isTrue();
|
||||
assertThat(parser.parse("/foo/{*elem}").hasPatternSyntax()).isTrue();
|
||||
assertThat(parser.parse("/f?o").hasPatternSyntax()).isTrue();
|
||||
assertThat(parser.parse("/f*").hasPatternSyntax()).isTrue();
|
||||
assertThat(parser.parse("/foo/{bar}/baz").hasPatternSyntax()).isTrue();
|
||||
|
||||
Reference in New Issue
Block a user