Opened 9 years ago

Closed 9 years ago

#216 closed design (fixed)

No-cache definition

Reported by: mnot@… Owned by:
Priority: normal Milestone: 11
Component: p6-cache Severity: Active WG Document
Keywords: Cc:

Description

2616's definition of the no-cache response directive <http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1> says:

If the no-cache directive does not specify a field-name, then a cache MUST NOT use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests.

This is misleading, because of the fuzzy definition of 'cacheable' in 2616. Our current text is:

The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to prevent caching even by caches that have been configured to return stale responses.

I propose this clarification:

""" The no-cache response directive indicates that the response MUST NOT be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to prevent a cache from using it to satisfy a request without contacting it, even by caches that have been configured to return stale responses. """

Change History (4)

comment:1 Changed 9 years ago by mnot@…

From [897]:

Refine definition of no-cache response directive (see #216).

comment:2 Changed 9 years ago by mnot@…

  • Milestone changed from unassigned to 11
  • Resolution set to incorporated
  • Status changed from new to closed

comment:3 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:4 Changed 9 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.