Ignore:
Timestamp:
Aug 5, 2008, 1:04:23 PM (11 years ago)
Author:
julian.reschke@…
Message:

Outdent comment about Date handling (this gets the list format closer to the intended format, see <http://www.w3.org/Protocols/HTTP/1.1/rfc2616.pdf>)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r302 r305  
    322322   The response &MUST; include the following header fields:
    323323  <list style="symbols">
    324     <t>Date, unless its omission is required by &clockless;</t>
    325   </list>
    326 </t>
    327 <t>
    328    If a clockless origin server obeys these rules, and proxies and
    329    clients add their own Date to any response received without one (as
    330    already specified by <xref target="RFC2068" x:sec="14.19" x:fmt=","/>), caches will operate
    331    correctly.
    332   <list style="symbols">
    333     <t>ETag and/or Content-Location, if the header would have been sent
    334         in a 200 response to the same request</t>
    335     <t>Expires, Cache-Control, and/or Vary, if the field-value might
    336         differ from that sent in any previous response for the same
    337         variant</t>
     324    <x:lt>
     325      <t>Date, unless its omission is required by &clockless;</t>
     326      <t>If a clockless origin server obeys these rules, and proxies and
     327         clients add their own Date to any response received without one (as
     328         already specified by <xref target="RFC2068" x:sec="14.19" x:fmt=","/>), caches will operate
     329         correctly.</t>
     330    </x:lt>
     331    <x:lt>
     332      <t>ETag and/or Content-Location, if the header would have been sent
     333          in a 200 response to the same request</t>
     334    </x:lt>
     335    <x:lt>
     336      <t>Expires, Cache-Control, and/or Vary, if the field-value might
     337          differ from that sent in any previous response for the same
     338          variant</t>
     339    </x:lt>
    338340  </list>
    339341</t>
Note: See TracChangeset for help on using the changeset viewer.