Ignore:
Timestamp:
Oct 7, 2009, 5:23:58 PM (10 years ago)
Author:
mnot@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r709 r710  
    11021102    <t>
    11031103      <x:h>Note:</x:h> This usage of the word private only controls where the response may
    1104       be stored, and cannot ensure the privacy of the message content.</t>
     1104      be stored, and cannot ensure the privacy of the message content.
     1105      Also, private response directives with field-names are often handled by
     1106      implementations as if an unqualified private directive was recieved; i.e.,
     1107      the special handling for the qualified form is not widely implemented.
     1108</t>
    11051109  </list>
    11061110</t>
     
    11221126    <t>
    11231127      <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey this directive.
     1128      Also, no-cache response directives with field-names are often handled by
     1129      implementations as if an unqualified no-cache directive was recieved; i.e.,
     1130      the special handling for the qualified form is not widely implemented.
    11241131    </t>
    11251132  </list>
     
    23232330      "Definition of 1xx Warn-Codes"
    23242331    </t>
     2332    <t>
     2333      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/169" />:
     2334      "private and no-cache CC directives with headers"
     2335    </t>
    23252336  </list>
    23262337</t>
Note: See TracChangeset for help on using the changeset viewer.