Ignore:
Timestamp:
Dec 7, 2012, 11:49:26 PM (7 years ago)
Author:
fielding@…
Message:

https scheme does not imply cache must be private; addresses #410

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2039 r2040  
    918918  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
    919919</artwork></figure>
    920 <t>
    921    Unlike the "http" scheme, responses to "https" identified requests
    922    are never "public" and thus &MUST-NOT; be reused for shared caching.
    923    They can, however, be reused in a private cache if the message is
    924    cacheable by default in HTTP or specifically indicated as such by
    925    the Cache-Control header field (&header-cache-control;).
    926 </t>
    927920<t>
    928921   Resources made available via the "https" scheme have no shared
Note: See TracChangeset for help on using the changeset viewer.