HTTP cache: explicit freshness and status codes

Issue #11325891 • Assigned to Steven K.

Details

Author
Mark N.
Created
Mar 20, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In HTTP, the status code doesn’t have much impact on caching. Specifically, if a response has an explicit freshness lifetime and there aren’t any other conditions preventing caching (e.g., method, other cache directives in the request or response), the status code doesn’t matter.

Allowing new status codes to be cached is important; it allows new extensions to be deployed without updating existing cache implementations.

In testing, Edge appears to only cache a few status codes, even when the response has explicit freshness information. The only ones I saw was 200. Other codes tested where Edge didn’t cache include 203, 204, 299, 400, 404, 410, 499, 500, 502, 503, 504, and 599.

Chrome caches all of these status codes when they have explicit freshness information.

Tests:
https://github.com/mnot/web-platform-tests/blob/http-cache/fetch/http-cache/status.html

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in