[html5] r4248 - [e] (0) Mention that sniffing the encoding violates HTTP. Fixing http://www.w3.o [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2009-10-21 02:50:28 -0700 (Wed, 21 Oct 2009)
New Revision: 4248

Modified:
   complete.html
   index
   source
Log:
[e] (0) Mention that sniffing the encoding violates HTTP.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7949

Modified: complete.html
===================================================================
--- complete.html	2009-10-21 09:41:18 UTC (rev 4247)
+++ complete.html	2009-10-21 09:50:28 UTC (rev 4248)
@@ -69927,7 +69927,16 @@
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
+  encoding declaration</a> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a href=#refsHTTP>[HTTP]</a> <a href=#refsRFC2046>[RFC2046]</a></p>
 
+
   <h5 id=character-encodings-0><span class=secno>11.2.2.2 </span>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252

Modified: index
===================================================================
--- index	2009-10-21 09:41:18 UTC (rev 4247)
+++ index	2009-10-21 09:50:28 UTC (rev 4248)
@@ -60990,7 +60990,16 @@
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class=note>This algorithm is a <a href=#willful-violation>willful violation</a>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <a href=#character-encoding-declaration>character
+  encoding declaration</a> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <a href=#character-encoding-declaration>character encoding declaration</a> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a href=#refsHTTP>[HTTP]</a> <a href=#refsRFC2046>[RFC2046]</a></p>
 
+
   <h5 id=character-encodings-0><span class=secno>9.2.2.2 </span>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252

Modified: source
===================================================================
--- source	2009-10-21 09:41:18 UTC (rev 4247)
+++ source	2009-10-21 09:50:28 UTC (rev 4248)
@@ -78683,7 +78683,17 @@
   as the user agent uses the returned value to select the decoder to
   use for the input stream.</p>
 
+  <p class="note">This algorithm is a <span>willful violation</span>
+  of the HTTP specification, which requires that the encoding be
+  assumed to be ISO-8859-1 in the absence of a <span>character
+  encoding declaration</span> to the contrary, and of the RFC 2046,
+  which requires that the encoding be assumed to be US-ASCII in the
+  absence of a <span>character encoding declaration</span> to the
+  contrary. This specification's third approach is motivated by a
+  desire to be maximally compatible with legacy content. <a
+  href="#refsHTTP">[HTTP]</a> <a href="#refsRFC2046">[RFC2046]</a></p>
 
+
   <h5>Character encodings</h5>
 
   <p>User agents must at a minimum support the UTF-8 and Windows-1252