W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2011

SSE; hixie: Make EventSource not reconnect for 2xx codes. (whatwg r5833)

From: poot <cvsmail@w3.org>
Date: Thu, 03 Feb 2011 18:50:10 -0500
To: public-html-diffs@w3.org
Message-Id: <E1Pl8wD-0008Fj-Un@jay.w3.org>
SSE; hixie: Make EventSource not reconnect for 2xx codes. (whatwg r5833)

http://dev.w3.org/cvsweb/html5/eventsource/Overview.html?r1=1.159&r2=1.160&f=h
http://html5.org/tools/web-apps-tracker?from=5832&to=5833

===================================================================
RCS file: /sources/public/html5/eventsource/Overview.html,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -d -r1.159 -r1.160
--- Overview.html	3 Feb 2011 23:41:59 -0000	1.159
+++ Overview.html	3 Feb 2011 23:48:59 -0000	1.160
@@ -553,15 +553,11 @@
   completed must <a href="#reestablish-the-connection">reestablish the connection</a>. This applies
   whether the connection is closed gracefully or unexpectedly. It
   doesn't apply for the error conditions listed below.<p>HTTP 200 OK responses that have a <span>Content-Type</span> 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>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 <a href="#reestablish-the-connection">reestablish the
-  connection</a>.<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>HTTP 305 Use Proxy, HTTP 401 Unauthorized, and 407 Proxy
+  than <code><a href="#text-event-stream">text/event-stream</a></code> (or some other supported type),
+  or that have no <span>Content-Type</span> 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
   other subresource.<p>HTTP 301 Moved Permanently, HTTP 302 Found, 303 See Other, and
   307 Temporary Redirect responses are handled by the <span title="fetch">fetching</span> algorithm. In the case of 301
@@ -571,16 +567,19 @@
   last 301 seen for requests for this object.<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 --><p>For non-HTTP protocols, UAs should act in equivalent ways.<hr><p>When a user agent is to <dfn id="announce-the-connection">announce the connection</dfn>, the
+  <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.<hr><p>When a user agent is to <dfn id="announce-the-connection">announce the connection</dfn>, the
   user agent must set the <code title="dom-EventSource-readyState"><a href="#dom-eventsource-readystate">readyState</a></code> attribute to
   <code title="dom-EventSource-OPEN"><a href="#dom-eventsource-open">OPEN</a></code> and <span>queue a
   task</span> to <span>fire a simple event</span> named <code title="event-open">open</code> at the
Received on Thursday, 3 February 2011 23:50:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 February 2011 23:50:12 GMT