{"version":"2.1.243","anchor":"gateway-loopback-escape-hatch-is-still-present","canonical_anchor":"gateway-loopback-escape-hatch-is-still-present","heading":"Gateway loopback escape hatch is still present","tier":"use","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243\/e\/gateway-loopback-escape-hatch-is-still-present","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.243","markdown":"### Gateway loopback escape hatch is still present\n\nPointing the gateway's key-set URL at a loopback address still needs that environment variable set.\n\n**What**\n\nAn earlier reading of this build suggested the check behind `CLAUDE_GATEWAY_ALLOW_LOOPBACK` had been removed. It has not: the check and its error text are unchanged, so pointing the gateway's key-set URL at a loopback address still requires that environment variable to be set.\n\n**Details**\n\n- The code moved position in the bundle rather than being deleted.\n- Without the variable, a loopback target is rejected with the message naming `cri.jwks_url`.\n\n**Evidence**\n\n`cri.jwks_url targets loopback but CLAUDE_GATEWAY_ALLOW_LOOPBACK is not set`\n\n- Area: Elsewhere\n- Names: `CLAUDE_GATEWAY_ALLOW_LOOPBACK`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}