Changeset 2047 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 09/12/12 16:54:07 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r2046 r2047 1193 1193 </t> 1194 1194 <t> 1195 New HTTP header fields &SHOULD;be registered with IANA in the1195 New HTTP header fields ought to be be registered with IANA in the 1196 1196 Message Header Field Registry, as described in &iana-header-registry;. 1197 Unrecognized header fields &MUST; be forwarded by a proxyunless the1197 A proxy &MUST; forward unrecognized header fields unless the 1198 1198 field-name is listed in the <x:ref>Connection</x:ref> header field 1199 1199 (<xref target="header.connection"/>) or the proxy is specifically 1200 configured to block or otherwise transformsuch fields.1201 Unrecognized header fields &SHOULD; be ignored by other recipients.1200 configured to block, or otherwise transform, such fields. 1201 Other recipients &SHOULD; ignore unrecognized header fields. 1202 1202 </t> 1203 1203 </section> … … 1216 1216 </t> 1217 1217 <t> 1218 Multiple header fields with the same field name &MUST-NOT; be 1219 sent in a message unless the entire field value for that 1220 header field is defined as a comma-separated list [i.e., #(values)]. 1218 A sender &MUST-NOT; generate multiple header fields with the same field 1219 name in a message unless either the entire field value for that 1220 header field is defined as a comma-separated list [i.e., #(values)] 1221 or the header field is a well-known exception (as noted below). 1221 1222 </t> 1222 1223 <t> … … 1873 1874 </artwork></figure> 1874 1875 <t> 1875 All transfer-coding names are case-insensitive and &SHOULD;be registered1876 All transfer-coding names are case-insensitive and ought to be registered 1876 1877 within the HTTP Transfer Coding registry, as defined in 1877 1878 <xref target="transfer.coding.registry"/>. … … 3086 3087 the family of Hypertext Transfer Protocols, as defined by the HTTP 3087 3088 version rules of <xref target="http.version"/> and future updates to this 3088 specification. Additional tokens canbe registered with IANA using the3089 specification. Additional tokens ought to be registered with IANA using the 3089 3090 registration procedure defined in <xref target="upgrade.token.registry"/>. 3090 3091 </t>
Note: See TracChangeset
for help on using the changeset viewer.