[Webkit-unassigned] [Bug 170716] New: HTTP Cache: Status Codes

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Apr 10 21:54:32 PDT 2017


            Bug ID: 170716
           Summary: HTTP Cache: Status Codes
           Product: WebKit
           Version: Safari Technology Preview
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mnot at mnot.net

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, Safari TP appears to cache some status codes, but does not cache unknown status codes (e.g., 299, 499, 599), nor does it cache 5xx-series status codes (e.g., 500, 502, 503, 504).

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


You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170411/f02f0c37/attachment.html>

More information about the webkit-unassigned mailing list