{"version":"2.1.259","anchor":"policy-limits-fetch-now-distinguishes-conditional-vs-uncondi","canonical_anchor":"policy-limits-fetch-now-distinguishes-conditional-vs-uncondi","heading":"Policy-limits fetch now distinguishes conditional vs unconditional 304 responses","tier":"notice","area":"Policy Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/policy-limits-fetch-now-distinguishes-conditional-vs-uncondi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Policy-limits fetch now distinguishes conditional vs unconditional 304 responses\n\nAn unexpected 304 to an unconditional policy-limits request is now a hard failure, and the 404 fast path was removed.\n\nAn unconditional (non-etag) request to the policy-limits endpoint that unexpectedly receives a 304 Not Modified response is now treated as a hard failure instead of being accepted as valid cached data. The 404 'no restrictions found' fast path has also been removed from this handler.\n\n- Area: Policy Limits\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}