Changeset 1101 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 08/01/11 14:27:21 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1099 r1101 15 15 <!ENTITY ID-MONTH "January"> 16 16 <!ENTITY ID-YEAR "2011"> 17 <!ENTITY mdash "—"> 17 18 <!ENTITY notation "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 18 19 <!ENTITY messaging "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 573 574 HTTP/1.1, and an example set of corresponding Reason-Phrase values, are 574 575 presented below. The reason phrases listed here are only 575 recommendations --they &MAY; be replaced by local equivalents without576 recommendations — they &MAY; be replaced by local equivalents without 576 577 affecting the protocol. 577 578 </t> … … 1159 1160 </artwork></figure> 1160 1161 <t> 1161 Other HTTP mechanisms can be used normally with the CONNECT method --1162 Other HTTP mechanisms can be used normally with the CONNECT method — 1162 1163 except end-to-end protocol Upgrade requests, since the 1163 1164 tunnel must be established first. … … 1854 1855 individuals no longer working at the server's site. It is not 1855 1856 necessary to mark all permanently unavailable resources as "gone" or 1856 to keep the mark for any length of time --that is left to the1857 to keep the mark for any length of time — that is left to the 1857 1858 discretion of the server owner. 1858 1859 </t> … … 2105 2106 </t> 2106 2107 <t> 2107 A proxy &MUST-NOT; modify the Allow header field --it does not need to2108 A proxy &MUST-NOT; modify the Allow header field — it does not need to 2108 2109 understand all the methods specified in order to handle them according to 2109 2110 the generic message handling rules. … … 2550 2551 <section title="Status Code Registry" anchor="status.code.registration"> 2551 2552 <t> 2552 The registration procedure for HTTP Status Codes --previously defined2553 in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> --is now defined2553 The registration procedure for HTTP Status Codes — previously defined 2554 in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> — is now defined 2554 2555 by <xref target="status.code.registry"/> of this document. 2555 2556 </t>
Note: See TracChangeset
for help on using the changeset viewer.