Changeset 1999 for draft-ietf-httpbis/latest/p7-auth.xml

Timestamp:

Nov 26, 2012, 7:10:52 PM (7 years ago)

Author:

mnot@…

Message:

Replace caching details with reference to p6; addresses #403.

File:

• draft-ietf-httpbis/latest/p7-auth.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p7-auth.xml

@@ -28 +28 @@
   <!ENTITY end-to-end.and-hop-by-hop    "<xref target='Part1' x:rel='#end-to-end.and.hop-by-hop.header-fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status.403                   "<xref target='Part2' x:rel='#status.403' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY caching-authenticated-responses "<xref target='Part6' x:rel='#caching.authenticated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
 <?rfc toc="yes" ?>
@@ -482 +482 @@
 </t>
 <t>
-      When a shared cache (see &shared-and-non-shared-caches;) receives a request
-      containing an Authorization field, it &MUST-NOT; return the
-      corresponding response as a reply to any other request, unless one
-      of the following specific exceptions holds:
-</t>
-<t>
-  <list style="numbers">
-      <t>If the response includes the "s-maxage" cache-control
-         directive, the cache &MAY; use that response in replying to a
-         subsequent request. But (if the specified maximum age has
-         passed) a proxy cache &MUST; first revalidate it with the origin
-         server, using the header fields from the new request to allow
-         the origin server to authenticate the new request. (This is the
-         defined behavior for s-maxage.) If the response includes "s-maxage=0",
-         the proxy &MUST; always revalidate it before re-using
-         it.</t>
-
-      <t>If the response includes the "must-revalidate" cache-control
-         directive, the cache &MAY; use that response in replying to a
-         subsequent request. But if the response is stale, all caches
-         &MUST; first revalidate it with the origin server, using the
-         header fields from the new request to allow the origin server
-         to authenticate the new request.</t>
-
-      <t>If the response includes the "public" cache-control directive,
-         it &MAY; be returned in reply to any subsequent request.</t>
-  </list>
+   See &caching-authenticated-responses; for details of and requirements
+   pertaining to handling of the Authorization field by HTTP caches.
 </t>
 </section>