You'll notice
A 304 response to a non-conditional remote settings request now raises an explicit error instead of quietly using the cache.
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.