Changeset 1240 for draft-ietf-httpbis/latest/p3-payload.xml
- Timestamp:
- 30/03/11 14:03:49 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.xml
r1234 r1240 368 368 <xref target="RFC2277"/>. 369 369 </t> 370 371 <section title="Missing Charset" anchor="missing.charset">372 <t>373 Some HTTP/1.0 software has interpreted a Content-Type header field without374 charset parameter incorrectly to mean "recipient should guess".375 Senders wishing to defeat this behavior &MAY; include a charset376 parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when377 it is known that it will not confuse the recipient.378 </t>379 <t>380 Unfortunately, some older HTTP/1.0 clients did not deal properly with381 an explicit charset parameter. HTTP/1.1 recipients &MUST; respect the382 charset label provided by the sender; and those user agents that have383 a provision to "guess" a charset &MUST; use the charset from the384 content-type field if they support that charset, rather than the385 recipient's preference, when initially displaying a document. See386 <xref target="canonicalization.and.text.defaults"/>.387 </t>388 </section>389 370 </section> 390 371 … … 555 536 data &MUST; be in a form defined above prior to being encoded. 556 537 </t> 557 <t>558 The "charset" parameter is used with some media types to define the559 character encoding (<xref target="character.sets"/>) of the data. When no explicit charset560 parameter is provided by the sender, media subtypes of the "text"561 type are defined to have a default charset value of "ISO-8859-1" when562 received via HTTP. Data in character encodings other than "ISO-8859-1" or563 its subsets &MUST; be labeled with an appropriate charset value. See564 <xref target="missing.charset"/> for compatibility problems.565 </t>566 538 </section> 567 539 … … 1089 1061 <t> 1090 1062 The special value "*", if present in the Accept-Charset field, 1091 matches every character encoding (including ISO-8859-1) which is not 1092 mentioned elsewhere in the Accept-Charset field. If no "*" is present 1093 in an Accept-Charset field, then all character encodings not explicitly 1094 mentioned get a quality value of 0, except for ISO-8859-1, which gets 1095 a quality value of 1 if not explicitly mentioned. 1063 matches every character encoding which is not mentioned elsewhere in the 1064 Accept-Charset field. If no "*" is present in an Accept-Charset field, then 1065 all character encodings not explicitly mentioned get a quality value of 0. 1096 1066 </t> 1097 1067 <t> … … 1722 1692 <references title="Normative References"> 1723 1693 1724 <reference anchor="ISO-8859-1">1725 <front>1726 <title>1727 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 11728 </title>1729 <author>1730 <organization>International Organization for Standardization</organization>1731 </author>1732 <date year="1998"/>1733 </front>1734 <seriesInfo name="ISO/IEC" value="8859-1:1998"/>1735 </reference>1736 1737 1694 <reference anchor="Part1"> 1738 1695 <front> … … 2601 2558 </t> 2602 2559 <t> 2560 Remove the default character encoding for text media types; the default 2561 now is whatever the media type definition says. 2562 (<xref target="canonicalization.and.text.defaults"/>) 2563 </t> 2564 <t> 2603 2565 Change ABNF productions for header fields to only define the field value. 2604 2566 (<xref target="header.fields"/>) 2567 </t> 2568 <t> 2569 Remove ISO-8859-1 special-casing in Accept-Charset. 2570 (<xref target="header.accept-charset"/>) 2605 2571 </t> 2606 2572 <t> … … 3076 3042 <list style="symbols"> 3077 3043 <t> 3044 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/20"/>: 3045 "Default charsets for text media types" 3046 </t> 3047 <t> 3078 3048 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>: 3079 3049 "untangle ABNFs for header fields"
Note: See TracChangeset
for help on using the changeset viewer.