2 Commits

Include renames

Author	SHA1	Message	Date
Brian Clozel	285182be27	Relax multiple segment matching constraints in PathPattern ... Prior to this commit, gh-35213 allowed wildcard path elments at the start of path patterns. This came with an additional constraint that rejected such patterns if the pattern segment following the wildcard one was not a literal: * `/**/{name}` was rejected * `/**/something/{name}` was accepted The motivation here was to make the performance impact of wildard patterns as small as possible at runtime. This commit relaxes this constraint because `/**/*.js` patterns are very popular in the security space for request matchers. Closes gh-35686	2025-11-05 18:32:44 +01:00
Brian Clozel	8bb63081a8	Document PathPattern matching for single/multiple segments ... This commit improves the reference document to better reflect the different between `*` or `{name}` on one side, and `**` or `{*path}` on the other. The former patterns only consider a single path segment and its content, while the latter variants consider zero or more path segments. This explains why `/test/{*path}` can match `/test`. Closes gh-35727	2025-11-05 14:58:58 +01:00