Changeset 1240 for draft-ietf-httpbis/latest/p3-payload.xml

Timestamp:

30/03/11 14:03:49 (11 years ago)

Author:

julian.reschke@…

Message:

Remove ISO-8859-1 default for text/*, remove special-case for ISO-8859-1 from Accept-Charset (see #20)

File:

• draft-ietf-httpbis/latest/p3-payload.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p3-payload.xml

@@ -368 +368 @@
    <xref target="RFC2277"/>.
 </t>
-
-<section title="Missing Charset" anchor="missing.charset">
-<t>
-   Some HTTP/1.0 software has interpreted a Content-Type header field without
-   charset parameter incorrectly to mean "recipient should guess".
-   Senders wishing to defeat this behavior &MAY; include a charset
-   parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when
-   it is known that it will not confuse the recipient.
-</t>
-<t>
-   Unfortunately, some older HTTP/1.0 clients did not deal properly with
-   an explicit charset parameter. HTTP/1.1 recipients &MUST; respect the
-   charset label provided by the sender; and those user agents that have
-   a provision to "guess" a charset &MUST; use the charset from the
-   content-type field if they support that charset, rather than the
-   recipient's preference, when initially displaying a document. See
-   <xref target="canonicalization.and.text.defaults"/>.
-</t>
-</section>
 </section>
 
@@ -555 +536 @@
    data &MUST; be in a form defined above prior to being encoded.
 </t>
-<t>
-   The "charset" parameter is used with some media types to define the
-   character encoding (<xref target="character.sets"/>) of the data. When no explicit charset
-   parameter is provided by the sender, media subtypes of the "text"
-   type are defined to have a default charset value of "ISO-8859-1" when
-   received via HTTP. Data in character encodings other than "ISO-8859-1" or
-   its subsets &MUST; be labeled with an appropriate charset value. See
-   <xref target="missing.charset"/> for compatibility problems.
-</t>
 </section>
 
@@ -1089 +1061 @@
 <t>
    The special value "*", if present in the Accept-Charset field,
-   matches every character encoding (including ISO-8859-1) which is not
-   mentioned elsewhere in the Accept-Charset field. If no "*" is present
-   in an Accept-Charset field, then all character encodings not explicitly
-   mentioned get a quality value of 0, except for ISO-8859-1, which gets
-   a quality value of 1 if not explicitly mentioned.
+   matches every character encoding which is not mentioned elsewhere in the
+   Accept-Charset field. If no "*" is present in an Accept-Charset field, then
+   all character encodings not explicitly mentioned get a quality value of 0.
 </t>
 <t>
@@ -1722 +1692 @@
 <references title="Normative References">
 
-<reference anchor="ISO-8859-1">
-  <front>
-    <title>
-     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
-    </title>
-    <author>
-      <organization>International Organization for Standardization</organization>
-    </author>
-    <date year="1998"/>
-  </front>
-  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
-</reference>
-
 <reference anchor="Part1">
   <front>
@@ -2601 +2558 @@
 </t>
 <t>
+  Remove the default character encoding for text media types; the default
+  now is whatever the media type definition says.
+  (<xref target="canonicalization.and.text.defaults"/>)
+</t>
+<t>
   Change ABNF productions for header fields to only define the field value.
   (<xref target="header.fields"/>)
+</t>
+<t>
+  Remove ISO-8859-1 special-casing in Accept-Charset.
+  (<xref target="header.accept-charset"/>)
 </t>
 <t>
@@ -3076 +3042 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/20"/>:
+      "Default charsets for text media types"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
       "untangle ABNFs for header fields"