Changeset 1737 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 08/07/12 13:02:45 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1735 r1737 29 29 <!ENTITY header-date "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 30 30 <!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'/>"> 31 32 <!ENTITY header-mime-version "<xref target='Part2' x:rel='#mime-version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 32 33 <!ENTITY header-pragma "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 2614 2615 response: 2615 2616 <list style="symbols"> 2616 <t> Expires</t>2617 <t><x:ref>Expires</x:ref> (&header-expires;)</t> 2617 2618 </list> 2618 2619 </t> 2619 2620 <t> 2620 2621 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 to2622 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. 2623 2624 </t> 2624 2625 <t> … … 4181 4182 </front> 4182 4183 <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> 4184 4187 </reference> 4185 4188
Note: See TracChangeset
for help on using the changeset viewer.