[Webkit-unassigned] [Bug 25129] New: Add support for cache-control: no-cache="foo"

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25129

           Summary: Add support for cache-control: no-cache="foo"
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: fishd at chromium.org
                CC: ap at webkit.org, ddkilzer at webkit.org


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.


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.