Ignore:
Timestamp:
Sep 2, 2011, 6:55:23 PM (8 years ago)
Author:
fielding@…
Message:

(editorial) Move Date and HTTP-date from p1 to p2.
Move bizarre clockless requirements to p4 (Last-Modified) and p6 (Expires)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1426 r1436  
    3131  <!ENTITY message-body             "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3232  <!ENTITY multipart-byteranges     "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    33   <!ENTITY full-date                "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     33  <!ENTITY http-date                "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3434  <!ENTITY qvalue                   "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3535  <!ENTITY uri                      "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    24162416<section title="Conversion of Date Formats" anchor="conversion.of.date.formats">
    24172417<t>
    2418    HTTP/1.1 uses a restricted set of date formats (&full-date;) to
     2418   HTTP/1.1 uses a restricted set of date formats (&http-date;) to
    24192419   simplify the process of date comparison. Proxies and gateways from
    24202420   other protocols &SHOULD; ensure that any Date header field present in a
     
    25832583<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
    25842584
    2585 <x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 6.4&gt;
     2585<x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 5.3&gt;
    25862586
    25872587<x:ref>subtype</x:ref> = token
Note: See TracChangeset for help on using the changeset viewer.