{"version":"2.1.267","anchor":"url-trust-check-simplified-reserved-name-special-case-re","canonical_anchor":"url-trust-check-simplified-reserved-name-special-case-re","heading":"URL trust check simplified \u2014 'reserved name' special case removed","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/url-trust-check-simplified-reserved-name-special-case-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### URL trust check simplified \u2014 'reserved name' special case removed\n\nURL trust checks simplified, dropping a separate 'reserved name' special case\n\n**Unclear.** The finding doesn't say what the removed 'reserved name' case covered or whether its behavior is now fully absorbed by the remaining checks.\n\n**What**\n\nThe internal check for whether a URL points to a trusted internal link is now a single combined check: it verifies the protocol is `https:`, runs a link-eligibility check, and confirms the path matches an allowed list of prefixes. A previous special case that separately handled certain 'reserved name' paths through its own dedicated function has been removed.\n\n**Why**\n\nThis simplifies the trust logic for internal links into one consistent rule, removing a separate carve-out that existed before.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}