[html5] r6848 - [giow] (1) Require implementations to ignore all MIME type parameters on text/ev [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-12-06 15:52:58 -0800 (Tue, 06 Dec 2011)
New Revision: 6848

Modified:
   complete.html
   index
   source
Log:
[giow] (1) Require implementations to ignore all MIME type parameters on text/event-stream resources
Affected topics: Server-Sent Events

Modified: complete.html
===================================================================
--- complete.html	2011-12-06 23:50:21 UTC (rev 6847)
+++ complete.html	2011-12-06 23:52:58 UTC (rev 6848)
@@ -76467,9 +76467,8 @@
   must act as follows.</p>
 
   <p>HTTP 200 OK responses with a <a href=#content-type>Content-Type</a> header
-  specifying the type <code><a href=#text/event-stream>text/event-stream</a></code>, either with no
-  parameters or with a single parameter with the name "<code title="">charset</code>" whose value is an <a href=#ascii-case-insensitive>ASCII
-  case-insensitive</a> match for the string "<code title="">utf-8</code>", must be processed line by line <a href=#event-stream-interpretation>as described below</a>.</p>
+  specifying the type <code><a href=#text/event-stream>text/event-stream</a></code>, ignoring any
+  <a href=#mime-type>MIME type</a> parameters, must be processed line by line <a href=#event-stream-interpretation>as described below</a>.</p>
 
   <p>When a successful response with a supported <a href=#mime-type>MIME
   type</a> is received, such that the user agent begins parsing the
@@ -76486,9 +76485,7 @@
   for the error conditions listed below.</p>
 
   <p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a>
-  specifying an unsupported type (including the
-  <code><a href=#text/event-stream>text/event-stream</a></code> type with unsupported parameters or
-  parameters with unsupported values), or that have no
+  specifying an unsupported type, or that have no
   <a href=#content-type>Content-Type</a> at all, must cause the user agent to
   <a href=#fail-the-connection>fail the connection</a>.</p> <!-- about:blank is defined as
   having no MIME type; javascript: as having the type text/html -->

Modified: index
===================================================================
--- index	2011-12-06 23:50:21 UTC (rev 6847)
+++ index	2011-12-06 23:52:58 UTC (rev 6848)
@@ -76467,9 +76467,8 @@
   must act as follows.</p>
 
   <p>HTTP 200 OK responses with a <a href=#content-type>Content-Type</a> header
-  specifying the type <code><a href=#text/event-stream>text/event-stream</a></code>, either with no
-  parameters or with a single parameter with the name "<code title="">charset</code>" whose value is an <a href=#ascii-case-insensitive>ASCII
-  case-insensitive</a> match for the string "<code title="">utf-8</code>", must be processed line by line <a href=#event-stream-interpretation>as described below</a>.</p>
+  specifying the type <code><a href=#text/event-stream>text/event-stream</a></code>, ignoring any
+  <a href=#mime-type>MIME type</a> parameters, must be processed line by line <a href=#event-stream-interpretation>as described below</a>.</p>
 
   <p>When a successful response with a supported <a href=#mime-type>MIME
   type</a> is received, such that the user agent begins parsing the
@@ -76486,9 +76485,7 @@
   for the error conditions listed below.</p>
 
   <p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a>
-  specifying an unsupported type (including the
-  <code><a href=#text/event-stream>text/event-stream</a></code> type with unsupported parameters or
-  parameters with unsupported values), or that have no
+  specifying an unsupported type, or that have no
   <a href=#content-type>Content-Type</a> at all, must cause the user agent to
   <a href=#fail-the-connection>fail the connection</a>.</p> <!-- about:blank is defined as
   having no MIME type; javascript: as having the type text/html -->

Modified: source
===================================================================
--- source	2011-12-06 23:50:21 UTC (rev 6847)
+++ source	2011-12-06 23:52:58 UTC (rev 6848)
@@ -88661,11 +88661,8 @@
   must act as follows.</p>
 
   <p>HTTP 200 OK responses with a <span>Content-Type</span> header
-  specifying the type <code>text/event-stream</code>, either with no
-  parameters or with a single parameter with the name "<code
-  title="">charset</code>" whose value is an <span>ASCII
-  case-insensitive</span> match for the string "<code
-  title="">utf-8</code>", must be processed line by line <a
+  specifying the type <code>text/event-stream</code>, ignoring any
+  <span>MIME type</span> parameters, must be processed line by line <a
   href="#event-stream-interpretation">as described below</a>.</p>
 
   <p>When a successful response with a supported <span>MIME
@@ -88683,9 +88680,7 @@
   for the error conditions listed below.</p>
 
   <p>HTTP 200 OK responses that have a <span>Content-Type</span>
-  specifying an unsupported type (including the
-  <code>text/event-stream</code> type with unsupported parameters or
-  parameters with unsupported values), or that have no
+  specifying an unsupported type, or that have no
   <span>Content-Type</span> at all, must cause the user agent to
   <span>fail the connection</span>.</p> <!-- about:blank is defined as
   having no MIME type; javascript: as having the type text/html -->