Ignore:
Timestamp:
Jul 8, 2012, 6:02:45 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink header field definitions(P6)

File:
1 edited

Legend:

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

    r1735 r1737  
    2929  <!ENTITY header-date            "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3030  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     31  <!ENTITY header-expires         "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3132  <!ENTITY header-mime-version    "<xref target='Part2' x:rel='#mime-version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3233  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    26142615   response:
    26152616  <list style="symbols">
    2616     <t>Expires</t>
     2617    <t><x:ref>Expires</x:ref> (&header-expires;)</t>
    26172618  </list>
    26182619</t>
    26192620<t>
    26202621   but it &MAY; add any of these fields if not already present. If an
    2621    Expires header field is added, it &MUST; be given a field-value identical to
    2622    that of the Date header field in that response.
     2622   <x:ref>Expires</x:ref> header field is added, it &MUST; be given a
     2623   field-value identical to that of the Date header field in that response.
    26232624</t>
    26242625<t>
     
    41814182  </front>
    41824183  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
    4183   <x:source href="p6-cache.xml" basename="p6-cache"/>
     4184  <x:source href="p6-cache.xml" basename="p6-cache">
     4185    <x:defines>Expires</x:defines>
     4186  </x:source>
    41844187</reference>
    41854188
Note: See TracChangeset for help on using the changeset viewer.