Skip to content
Permalink
Browse files

[giow] (1) Make EventSource not reconnect for 2xx codes.

git-svn-id: http://svn.whatwg.org/webapps@5833 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Feb 3, 2011
1 parent 7171d04 commit 5a5952368c65d3fb16d0be570b8ebb703e68c243
Showing with 36 additions and 46 deletions.
  1. +18 −23 complete.html
  2. +18 −23 source
doesn't apply for the error conditions listed below.</p>

<p>HTTP 200 OK responses that have a <a href=#content-type>Content-Type</a> other
than <code><a href=#text/event-stream>text/event-stream</a></code> (or some other supported type)
must cause the user agent to <a href=#fail-the-connection>fail the connection</a>.</p>

<p>HTTP 204 No Content, and 205 Reset Content responses are
equivalent to 200 OK responses with the right <a href=#mime-type>MIME type</a>
but no content, and thus must <a href=#reestablish-the-connection>reestablish the
connection</a>.</p>

<p>Other HTTP response codes in the 2xx range <!--201 Created, 202
Accepted, 203 Non-Authoritative Information, and 206 Partial
Content-->must similarly <a href=#reestablish-the-connection>reestablish the connection</a>. They
are, however, likely to indicate an error has occurred somewhere and
may cause the user agent to emit a warning.</p>
than <code><a href=#text/event-stream>text/event-stream</a></code> (or some other supported 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 -->

<p>HTTP 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
<p>Any other HTTP response code not listed here, and any network
error that prevents the HTTP connection from being established in
the first place (e.g. DNS errors), must cause the user agent to
<a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 300
Multiple Choices, HTTP 304 Not Modified, HTTP 400 Bad Request, 403
Forbidden, 404 Not Found, 405 Method Not Allowed, 406 Not
Acceptable, 408 Request Timeout, 409 Conflict, 410 Gone, 411 Length
Required, 412 Precondition Failed, 413 Request Entity Too Large, 414
Request-URI Too Long, 415 Unsupported Media Type, 416 Requested
Range Not Satisfiable, 417 Expectation Failed, 500 Internal Server
Error, 501 Not Implemented, 502 Bad Gateway, 503 Service
Unavailable, 504 Gateway Timeout, and 505 HTTP Version Not Supported
responses -->
<a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 201
Created, HTTP 202 Accepted, HTTP 203 Non-Authoritative Information,
HTTP 204 No Content, HTTP 205 Reset Content, HTTP 206 Partial
Content, HTTP 300 Multiple Choices, HTTP 304 Not Modified, HTTP 400
Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not Allowed,
406 Not Acceptable, 408 Request Timeout, 409 Conflict, 410 Gone, 411
Length Required, 412 Precondition Failed, 413 Request Entity Too
Large, 414 Request-URI Too Long, 415 Unsupported Media Type, 416
Requested Range Not Satisfiable, 417 Expectation Failed, 500
Internal Server Error, 501 Not Implemented, 502 Bad Gateway, 503
Service Unavailable, 504 Gateway Timeout, and 505 HTTP Version Not
Supported responses --> <!-- mailto: is defined as equivalent to
HTTP 204 -->

<p>For non-HTTP protocols, UAs should act in equivalent ways.</p>

41 source
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)
must cause the user agent to <span>fail the connection</span>.</p>

<p>HTTP 204 No Content, and 205 Reset Content responses are
equivalent to 200 OK responses with the right <span>MIME type</span>
but no content, and thus must <span>reestablish the
connection</span>.</p>

<p>Other HTTP response codes in the 2xx range <!--201 Created, 202
Accepted, 203 Non-Authoritative Information, and 206 Partial
Content-->must similarly <span>reestablish the connection</span>. They
are, however, likely to indicate an error has occurred somewhere and
may cause the user agent to emit a warning.</p>
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 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
<p>Any other HTTP response code not listed here, and any network
error that prevents the HTTP connection from being established in
the first place (e.g. DNS errors), must cause the user agent to
<span>fail the connection</span>.</p> <!-- including: HTTP 300
Multiple Choices, HTTP 304 Not Modified, HTTP 400 Bad Request, 403
Forbidden, 404 Not Found, 405 Method Not Allowed, 406 Not
Acceptable, 408 Request Timeout, 409 Conflict, 410 Gone, 411 Length
Required, 412 Precondition Failed, 413 Request Entity Too Large, 414
Request-URI Too Long, 415 Unsupported Media Type, 416 Requested
Range Not Satisfiable, 417 Expectation Failed, 500 Internal Server
Error, 501 Not Implemented, 502 Bad Gateway, 503 Service
Unavailable, 504 Gateway Timeout, and 505 HTTP Version Not Supported
responses -->
<span>fail the connection</span>.</p> <!-- including: HTTP 201
Created, HTTP 202 Accepted, HTTP 203 Non-Authoritative Information,
HTTP 204 No Content, HTTP 205 Reset Content, HTTP 206 Partial
Content, HTTP 300 Multiple Choices, HTTP 304 Not Modified, HTTP 400
Bad Request, 403 Forbidden, 404 Not Found, 405 Method Not Allowed,
406 Not Acceptable, 408 Request Timeout, 409 Conflict, 410 Gone, 411
Length Required, 412 Precondition Failed, 413 Request Entity Too
Large, 414 Request-URI Too Long, 415 Unsupported Media Type, 416
Requested Range Not Satisfiable, 417 Expectation Failed, 500
Internal Server Error, 501 Not Implemented, 502 Bad Gateway, 503
Service Unavailable, 504 Gateway Timeout, and 505 HTTP Version Not
Supported responses --> <!-- mailto: is defined as equivalent to
HTTP 204 -->

<p>For non-HTTP protocols, UAs should act in equivalent ways.</p>

0 comments on commit 5a59523

Please sign in to comment.