Under the hood
Useful2 Signal0
Wildcard URL patterns are now parsed by a shared helper, including odd cases like a wildcard in the port.
What's wrong with this entry?
Anonymous. No account, no email.
What
Wildcard URL patterns are now parsed by a dedicated helper instead of ad-hoc string handling, used to decide which URL component a template variable expands into.
Details
- the helper substitutes a sentinel for
*, parses the result as a URL, and retries with a placeholder port when the wildcard sits in the port position - it returns the URL components with the sentinel mapped back to
* - callers use it to classify an expansion as scheme, authority, or the rest, for MCP-style URL templates
- the security consequence of the change could not be fully established
Evidence
pathname
Strings lifted out of the shipped bundle, so the claim above can be checked against them.