[giow] (2) Since this made it likely that overloaded servers would ju…

…st get even more overloaded, pull back a little and let all 5xx errors stop EventSource reconnects. It still reconnects if the connection drops, though. (Compat: 5xxs don't cause reconnects in deployed browsers currently as far as I can tell.)

Affected topics: HTML

git-svn-id: http://svn.whatwg.org/webapps@7634 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 31 December 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 2 January 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -83162,19 +83162,20 @@ <h4 id=processing-model-7><span class=secno>10.2.3 </span>Processing model</h4>
   resource for this <code><a href=#eventsource>EventSource</a></code> object start with the URL given for the last 301 seen
   for requests for this object.</p>
 
-  <p>HTTP 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway
-  Timeout responses, and any network error that prevents the connection from being established in
-  the first place (e.g. DNS errors), must cause the user agent to asynchronously <a href=#reestablish-the-connection>reestablish
-  the connection</a>.</p>
-
-  <p>Any other HTTP response code not listed here must cause the user agent to <a href=#fail-the-connection>fail the
-  connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203 Non-Authoritative
-  Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300 Multiple Choices, 304 Not
-  Modified, 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, 501 Not Implemented, and 505 HTTP Version
-  Not Supported responses --> <!-- mailto: is defined as equivalent to HTTP 204 -->
+  <p id=event-source-network-errors-reconnect>Network errors that prevents the connection from
+  being established in the first place (e.g. DNS errors), must cause the user agent to
+  asynchronously <a href=#reestablish-the-connection>reestablish the connection</a>.</p>
+
+  <p id=event-source-fail-reasons>Any other HTTP response code not listed here must cause the user
+  agent to <a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
+  Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
+  Multiple Choices, 304 Not Modified, 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, HTTP 500 Internal Server Error,
+  501 Not Implemented, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout responses,
+  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>
 

index

@@ -248,7 +248,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 31 December 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 2 January 2013</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -83162,19 +83162,20 @@ dictionary <dfn id=eventsourceinit>EventSourceInit</dfn> {
   resource for this <code><a href=#eventsource>EventSource</a></code> object start with the URL given for the last 301 seen
   for requests for this object.</p>
 
-  <p>HTTP 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway
-  Timeout responses, and any network error that prevents the connection from being established in
-  the first place (e.g. DNS errors), must cause the user agent to asynchronously <a href=#reestablish-the-connection>reestablish
-  the connection</a>.</p>
-
-  <p>Any other HTTP response code not listed here must cause the user agent to <a href=#fail-the-connection>fail the
-  connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203 Non-Authoritative
-  Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300 Multiple Choices, 304 Not
-  Modified, 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, 501 Not Implemented, and 505 HTTP Version
-  Not Supported responses --> <!-- mailto: is defined as equivalent to HTTP 204 -->
+  <p id=event-source-network-errors-reconnect>Network errors that prevents the connection from
+  being established in the first place (e.g. DNS errors), must cause the user agent to
+  asynchronously <a href=#reestablish-the-connection>reestablish the connection</a>.</p>
+
+  <p id=event-source-fail-reasons>Any other HTTP response code not listed here must cause the user
+  agent to <a href=#fail-the-connection>fail the connection</a>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
+  Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
+  Multiple Choices, 304 Not Modified, 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, HTTP 500 Internal Server Error,
+  501 Not Implemented, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout responses,
+  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>
 

source

@@ -96486,19 +96486,20 @@ dictionary <dfn>EventSourceInit</dfn> {
   resource for this <code>EventSource</code> object start with the URL given for the last 301 seen
   for requests for this object.</p>
 
-  <p>HTTP 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway
-  Timeout responses, and any network error that prevents the connection from being established in
-  the first place (e.g. DNS errors), must cause the user agent to asynchronously <span>reestablish
-  the connection</span>.</p>
-
-  <p>Any other HTTP response code not listed here must cause the user agent to <span>fail the
-  connection</span>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203 Non-Authoritative
-  Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300 Multiple Choices, 304 Not
-  Modified, 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, 501 Not Implemented, and 505 HTTP Version
-  Not Supported responses --> <!-- mailto: is defined as equivalent to HTTP 204 -->
+  <p id="event-source-network-errors-reconnect">Network errors that prevents the connection from
+  being established in the first place (e.g. DNS errors), must cause the user agent to
+  asynchronously <span>reestablish the connection</span>.</p>
+
+  <p id="event-source-fail-reasons">Any other HTTP response code not listed here must cause the user
+  agent to <span>fail the connection</span>.</p> <!-- including: HTTP 201 Created, 202 Accepted, 203
+  Non-Authoritative Information, 204 No Content, 205 Reset Content, 206 Partial Content, 300
+  Multiple Choices, 304 Not Modified, 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, HTTP 500 Internal Server Error,
+  501 Not Implemented, 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout responses,
+  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>