{"version":"2.1.259","anchor":"remote-settings-304-mismatch-now-surfaces-as-an-error","canonical_anchor":"remote-settings-304-mismatch-now-surfaces-as-an-error","heading":"Remote settings 304 mismatch now surfaces as an error","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/remote-settings-304-mismatch-now-surfaces-as-an-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Remote settings 304 mismatch now surfaces as an error\n\nA 304 response to a non-conditional remote settings request now raises an explicit error instead of quietly using the cache.\n\nIf the server responds with HTTP 304 Not Modified to a request that was not conditional (no cached ETag was sent), this now surfaces as an explicit error, \"Unexpected 304 Not Modified\", with `skipRetry` set, instead of silently falling back to cached remote settings.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}