{"version":"2.1.281","anchor":"claude-gateway-allow-loopback-helpers-restructured-in-gatewa","canonical_anchor":"claude-gateway-allow-loopback-helpers-restructured-in-gatewa","heading":"CLAUDE_GATEWAY_ALLOW_LOOPBACK helpers restructured in gateway module","tier":"internal","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claude-gateway-allow-loopback-helpers-restructured-in-gatewa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### CLAUDE_GATEWAY_ALLOW_LOOPBACK helpers restructured in gateway module\n\nThe code reading CLAUDE_GATEWAY_ALLOW_LOOPBACK was reorganised; the variable still lets the gateway reach loopback addresses\n\n**Unclear.** The finding does not say whether the new state object or timing values change behaviour.\n\n**What**\n\n`CLAUDE_GATEWAY_ALLOW_LOOPBACK` still lets the gateway reach loopback addresses, which are addresses pointing back to the same computer. The code that reads it and applies the loopback checks moved into new shared helpers, with a state object that starts disabled and some timing values.\n\n**Why**\n\nThe variable's meaning is the same, so settings that already use it need no change.\n\n- Area: Gateway\n- Names: `CLAUDE_GATEWAY_ALLOW_LOOPBACK`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}