{"version":"2.1.304","anchor":"policy-limits-304-without-an-anthropic-request-id-is-treate","canonical_anchor":"policy-limits-304-without-an-anthropic-request-id-is-treate","heading":"An 'unchanged' policy reply without Anthropic's request id is no longer trusted","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/policy-limits-304-without-an-anthropic-request-id-is-treate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### An 'unchanged' policy reply without Anthropic's request id is no longer trusted\n\nClaude Code now treats some 'not modified' replies about organisation policy limits as coming from a middleman and keeps its cached copy\n\n**What**\n\nPolicy limits are restrictions your organisation sets on Claude Code. Claude Code fetches them and keeps a cached copy. When it checks for updates, the server can answer 304, meaning \"not modified\".\n\nBefore, any 304 meant Claude Code would use its cached restrictions. Now, in some cases, a 304 that lacks Anthropic's request id is treated as coming from something between you and Anthropic, such as a proxy. Claude Code then:\n\n- counts the fetch as failed\n\n- does not retry\n\n- keeps the restrictions it already had cached\n\nThe tag Claude Code sends to ask whether the policy changed is also now worked out differently.\n\n**Why**\n\nA proxy or captive portal (a network login page, such as on public wifi) can no longer pass itself off as Anthropic and claim the policy has not changed.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}