Skip to content

Commit

Permalink
[giow] (1) Require implementations to ignore all MIME type parameters…
Browse files Browse the repository at this point in the history
… on text/event-stream resources

Affected topics: Server-Sent Events

git-svn-id: http://svn.whatwg.org/webapps@6848 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Dec 6, 2011
1 parent d10529f commit d97166b
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 20 deletions.
9 changes: 3 additions & 6 deletions complete.html
Expand Up @@ -76467,9 +76467,8 @@ <h4 id=processing-model-5><span class=secno>10.2.3 </span>Processing model</h4>
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
Expand All @@ -76486,9 +76485,7 @@ <h4 id=processing-model-5><span class=secno>10.2.3 </span>Processing model</h4>
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 -->
Expand Down
9 changes: 3 additions & 6 deletions index
Expand Up @@ -76467,9 +76467,8 @@ dictionary <dfn id=eventsourceinit>EventSourceInit</dfn> {
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
Expand All @@ -76486,9 +76485,7 @@ dictionary <dfn id=eventsourceinit>EventSourceInit</dfn> {
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 -->
Expand Down
11 changes: 3 additions & 8 deletions source
Expand Up @@ -88661,11 +88661,8 @@ dictionary <dfn>EventSourceInit</dfn> {
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
Expand All @@ -88683,9 +88680,7 @@ dictionary <dfn>EventSourceInit</dfn> {
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 -->
Expand Down

0 comments on commit d97166b

Please sign in to comment.