HTML5 Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/6250

SVNBugCommentTime (UTC)
6250[Gecko] [Internet Explorer] [Opera] [Webkit] EventSource: only allow text/event-stream with no parameters or with a charset=utf-8 parameter.2011-06-16 23:07
Index: source
===================================================================
--- source	(revision 6249)
+++ source	(revision 6250)
@@ -89500,13 +89500,16 @@
   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> must be processed
-  line by line <a href="#event-stream-interpretation">as described
+  specifying the type <code>text/event-stream</code>, either with no
+  parameters or with a single parameter whose name is "<code
+  title="">charset</code>" and whose value is an <span>ASCII
+  case-insensitive match</span> for "UTF-8", 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 type</span> is
-  received, such that the user agent begins parsing the contents of
-  the stream, the user agent must <span>announce the
+  <p>When a successful response with a supported <span>MIME
+  type</span> is received, such that the user agent begins parsing the
+  contents of the stream, the user agent must <span>announce the
   connection</span>.</p>
 
   <p>The <span title="concept-task">task</span> that the
@@ -89517,12 +89520,13 @@
   whether the connection is closed gracefully or unexpectedly. It
   doesn't apply for the error conditions listed below.</p>
 
-  <p>HTTP 200 OK responses that have a <span>Content-Type</span> other
-  than <code>text/event-stream</code> (or some other supported 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 -->
+  <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
+  <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 -->
 
   <p>HTTP 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy
   Authentication Required should be treated transparently as for any

|