Recently, we hypothesized that most XHR responses are probably not worth caching. I think that, absent a really strong indicator that we should cache an XHR response, we should throw them away by default. I suggest we design a couple of policies (e.g. "no heuristic caching for XHR", "only cache XHR in memory"), and then design and deploy some telemetry that tells us what the difference in cache hit rate and the difference in replaced-without-a-hit would be, before we make the actual change.
there have been a number of cases where people expect just the opposite. Its critical that we honor no-cache on the request side tho (different bug)
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.