Bug 25129
| Summary: | Add support for cache-control: no-cache="foo" | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Darin Fisher (:fishd, Google) <fishd> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ap, ddkilzer |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Darin Fisher (:fishd, Google)
Add support for cache-control: no-cache="foo"
From RFC 2616 section 14.9.1:
If the no-cache directive does specify one or more field-names,
then a cache MAY use the response to satisfy a subsequent request,
subject to any other restrictions on caching. However, the
specified field-name(s) MUST NOT be sent in the response to a
subsequent request without successful revalidation with the origin
server. This allows an origin server to prevent the re-use of
certain header fields in a response, while still allowing caching
of the rest of the response.
So, it is not correct to treat no-cache="foo" as equivalent to no-cache. Doing so means missing out on opportunities to cache content.
See bug 24656 for related discussion.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Antti Koivisto
The patch in bug 13128 wil fix this as well.
*** This bug has been marked as a duplicate of 13128 ***