I am experiencing an issue due to the okhttp caching behavior that existed in versions prior to okhttp 3.4.0. When a network response comes back with a 200 status code where the Last-Modified header is older than the cached response, it combines the headers including the ETag from the network response, but keeps the old cached content. This results in persistent error where the cached response is a maintenance page, but the ETag corresponds to the appropriate JSON response. Going forward, we keep getting 304 status codes even though the cached content doesn't really match the ETag.