25129 2009-04-09 22:51:22 -0700 Add support for cache-control: no-cache="foo" 2009-06-03 17:11:56 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) All All RESOLVED DUPLICATE 13128 P2 Normal --- 1 fishd webkit-unassigned ap ddkilzer oldest_to_newest 117121 0 fishd 2009-04-09 22:51:22 -0700 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. 124256 1 koivisto 2009-06-03 17:11:56 -0700 The patch in bug 13128 wil fix this as well. *** This bug has been marked as a duplicate of 13128 ***