Changeset 1975 for draft-ietf-httpbis/latest/p1-messaging.xml
- Timestamp:
- 05/11/12 05:10:11 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.xml
r1973 r1975 20 20 <!ENTITY cache-incomplete "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 21 <!ENTITY payload "<xref target='Part2' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 22 <!ENTITY media-type s "<xref target='Part2' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">22 <!ENTITY media-type "<xref target='Part2' x:rel='#media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 23 23 <!ENTITY content-codings "<xref target='Part2' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 24 24 <!ENTITY CONNECT "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1310 1310 <t> 1311 1311 Historically, HTTP has allowed field content with text in the ISO-8859-1 1312 <xref target="ISO-8859-1"/> char acter encoding and supported other1313 character sets onlythrough use of <xref target="RFC2047"/> encoding.1312 <xref target="ISO-8859-1"/> charset, supporting other charsets only 1313 through use of <xref target="RFC2047"/> encoding. 1314 1314 In practice, most HTTP header field values use only a subset of the 1315 US-ASCII char acter encoding<xref target="USASCII"/>. Newly defined1315 US-ASCII charset <xref target="USASCII"/>. Newly defined 1316 1316 header fields &SHOULD; limit their field values to US-ASCII octets. 1317 Recipients &SHOULD; treat other (obs-text) octets in field contentas1317 Recipients &SHOULD; treat other octets in field content (obs-text) as 1318 1318 opaque data. 1319 1319 </t>
Note: See TracChangeset
for help on using the changeset viewer.