{"version":"2.1.236","anchor":"an-origin-normalising-helper-with-nothing-calling-it","canonical_anchor":"an-origin-normalising-helper-with-nothing-calling-it","heading":"An origin-normalising helper with nothing calling it","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/an-origin-normalising-helper-with-nothing-calling-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### An origin-normalising helper with nothing calling it\n\nA strict URL-to-origin helper exists next to the claude.ai origin code, with nothing calling it.\n\n**What**\n\nA new function beside the claude.ai origin resolver turns a URL into a bare scheme-and-host origin. It upgrades `wss:` to `https:`, allows `ws:` and `http:` only for loopback hosts (localhost, 127.0.0.1, ::1 or any 127.x.x.x address), and returns nothing if the URL carries credentials, a path, a query or a fragment.\n\n**Details**\n\n- Its symbol appears only at its own definition in the bundle; nothing calls it.\n- The neighbouring origin-override hook that the resolver consults has a body of a bare `return;`, so it always yields nothing and the resolver always falls back to the configured `CLAUDE_AI_ORIGIN`.\n- Together these look like groundwork for a configurable or localhost artifact origin that nothing selects yet.\n\n**Evidence**\n\n`\"wss:\"`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}