{"version":"2.1.219","anchor":"wildcard-url-patterns-parsed-through-a-dedicated-helper","canonical_anchor":"wildcard-url-patterns-parsed-through-a-dedicated-helper","heading":"Wildcard URL patterns parsed through a dedicated helper","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/wildcard-url-patterns-parsed-through-a-dedicated-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Wildcard URL patterns parsed through a dedicated helper\n\nWildcard URL patterns are now parsed by a shared helper, including odd cases like a wildcard in the port.\n\n**What**\n\nWildcard 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.\n\n**Details**\n\n- 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\n- it returns the URL components with the sentinel mapped back to `*`\n- callers use it to classify an expansion as scheme, authority, or the rest, for MCP-style URL templates\n- the security consequence of the change could not be fully established\n\n**Evidence**\n\n`pathname`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}