If 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.
Remote settings 304 mismatch now surfaces as an error
A 304 response to a non-conditional remote settings request now raises an explicit error instead of quietly using the cache.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.259,
Bug FixesSection of the release