Bug 25129 - Add support for cache-control: no-cache="foo"
Summary: Add support for cache-control: no-cache="foo"
Status: RESOLVED DUPLICATE of bug 13128
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2009-04-09 22:51 PDT by Darin Fisher (:fishd, Google)
Modified: 2009-06-03 17:11 PDT (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Darin Fisher (:fishd, Google) 2009-04-09 22:51:22 PDT
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.
Comment 1 Antti Koivisto 2009-06-03 17:11:56 PDT
The patch in bug 13128 wil fix this as well.

*** This bug has been marked as a duplicate of 13128 ***