spring-framework

34036 Commits

19 Branches

147 Tags

391 MiB

Tree: d0f57013b0

Commit Graph

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	6 months ago
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	6 months ago

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

6 months ago

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

6 months ago

2 Commits (d0f57013b0ae9e716b370a28d4dcac40778ea4e7)