Changeset 710 for draft-ietf-httpbis/latest

Timestamp:

08/10/09 00:23:58 (13 years ago)

Author:

mnot@…

Message:

note that qualified forms of cc: private and no-cache aren't often implemented (see #169)

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (3 diffs)
• p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -1101 +1101 @@
          </dd>
          <dd> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
-            content.
+            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
+            directive was recieved; i.e., the special handling for the qualified form is not widely implemented.
          </dd>
       </dl>
@@ -1114 +1115 @@
             server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
          </dd>
-         <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive.
+         <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
+            handled by implementations as if an unqualified no-cache directive was recieved; i.e., the special handling for the qualified
+            form is not widely implemented.
          </dd>
       </dl>
@@ -1726 +1729 @@
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/54">http://tools.ietf.org/wg/httpbis/trac/ticket/54</a>&gt;: "Definition of 1xx Warn-Codes"
          </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/169">http://tools.ietf.org/wg/httpbis/trac/ticket/169</a>&gt;: "private and no-cache CC directives with headers"
+         </li>
       </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -1102 +1102 @@
     <t>
       <x:h>Note:</x:h> This usage of the word private only controls where the response may
-      be stored, and cannot ensure the privacy of the message content.</t>
+      be stored, and cannot ensure the privacy of the message content.
+      Also, private response directives with field-names are often handled by
+      implementations as if an unqualified private directive was recieved; i.e.,
+      the special handling for the qualified form is not widely implemented.
+</t>
   </list>
 </t>
@@ -1122 +1126 @@
     <t>
       <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey this directive.
+      Also, no-cache response directives with field-names are often handled by
+      implementations as if an unqualified no-cache directive was recieved; i.e.,
+      the special handling for the qualified form is not widely implemented.
     </t>
   </list>
@@ -2323 +2330 @@
       "Definition of 1xx Warn-Codes"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/169" />:
+      "private and no-cache CC directives with headers"
+    </t>
   </list>
 </t>