Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[go] (2) <eventsource>: clarify error handling rules.
git-svn-id: http://svn.whatwg.org/webapps@2359 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Oct 21, 2008
1 parent 7c0d065 commit 95ca172
Show file tree
Hide file tree
Showing 2 changed files with 54 additions and 56 deletions.
55 changes: 27 additions & 28 deletions index
Expand Up @@ -41344,30 +41344,31 @@ XXX Once we resolve the style="" issue, address these:
user agents should ignore HTTP cache headers, and instead assume
that the resource indicates that it does not wish to be cached.</p>

<p>If such a resource completes loading (i.e. the entire HTTP
response body is received or the connection itself closes), the user
agent should request the event source resource again after a delay
equal to the reconnection time of the event source.</p>
<p>If such a resource (with the correct MIME type) completes loading
(i.e. the entire HTTP response body is received or the connection
itself closes), the user agent should request the event source
resource again after a delay equal to the reconnection time of the
event source. This doesn't apply for the error cases that are listed
below.</p>

<p>HTTP 200 OK responses that have a <a href=#content-type-0>Content-Type</a> other
than <code>text/event-stream</code> (or some other supported type),
and HTTP responses whose Access-Control headers indicate that the
resource are not to be used, must be ignored and must prevent the
user agent from refetching the resource for that event source.</p>

<p>HTTP 201 Created, 202 Accepted, 203 Non-Authoritative
Information, and 206 Partial Content responses must be treated like
HTTP 200 OK responses for the purposes of reopening event source
resources. They are, however, likely to indicate an error has
occurred somewhere and may cause the user agent to emit a
warning.</p>
resource are not to be used, must be ignored.</p>

<p>HTTP 204 No Content, and 205 Reset Content responses must be
treated as if they were 200 OK responses with the right MIME type
but no content, and should therefore cause the user agent to refetch
the resource after a delay equal to the reconnection time of the
event source.</p>

<p>Other HTTP response codes in the 2xx range <!--201 Created, 202
Accepted, 203 Non-Authoritative Information, and 206 Partial
Content-->must be treated like HTTP 200 OK responses for the
purposes of reopening event source resources. They are, however,
likely to indicate an error has occurred somewhere and may cause the
user agent to emit a warning.</p>

<p>HTTP 300 Multiple Choices responses should be handled
automatically if possible (treating the responses as if they were
302 Found responses pointing to the appropriate resource), and
Expand Down Expand Up @@ -41395,19 +41396,16 @@ XXX Once we resolve the style="" issue, address these:
Authentication Required should be treated transparently as for any
other subresource.</p>

<p>Any other HTTP response code not listed here should cause the
user agent to stop trying to process this event source.</p> <!--
including: 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>DNS errors must be considered fatal, and cause the user agent to
not open any connection for that event source.</p>
<p>Any other HTTP response code not listed here or network error
(e.g. DNS errors) must be ignored.</p> <!-- including: 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.</p>

Expand Down Expand Up @@ -52922,8 +52920,9 @@ interface <dfn id=timeouthandler>TimeoutHandler</dfn> {
Stuart Parmenter, Sunava Dutta, Tantek &Ccedil;elik, Terrence Wood,
Thomas Broyer, Thomas O'Connor, Tim Altman, Tim Johansson, Travis
Leithead, Tyler Close, Vladimir Vuki&#263;evi&#263;, Wakaba,
Wayne Pollock, William Swanson, Yi-An Huang, and &Oslash;istein
E. Andersen, for their useful and substantial comments.</p>
Wayne Pollock, Wellington Fernando de Macedo, William Swanson, Yi-An
Huang, and &Oslash;istein E. Andersen, for their useful and
substantial comments.</p>

<p>Thanks also to everyone who has ever posted about HTML5 to their
blogs, public mailing lists, or forums, including the <a href=http://lists.w3.org/Archives/Public/public-html/>W3C
Expand Down
55 changes: 27 additions & 28 deletions source
Expand Up @@ -47105,30 +47105,31 @@ XXX Once we resolve the style="" issue, address these:
user agents should ignore HTTP cache headers, and instead assume
that the resource indicates that it does not wish to be cached.</p>

<p>If such a resource completes loading (i.e. the entire HTTP
response body is received or the connection itself closes), the user
agent should request the event source resource again after a delay
equal to the reconnection time of the event source.</p>
<p>If such a resource (with the correct MIME type) completes loading
(i.e. the entire HTTP response body is received or the connection
itself closes), the user agent should request the event source
resource again after a delay equal to the reconnection time of the
event source. This doesn't apply for the error cases that are 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),
and HTTP responses whose Access-Control headers indicate that the
resource are not to be used, must be ignored and must prevent the
user agent from refetching the resource for that event source.</p>

<p>HTTP 201 Created, 202 Accepted, 203 Non-Authoritative
Information, and 206 Partial Content responses must be treated like
HTTP 200 OK responses for the purposes of reopening event source
resources. They are, however, likely to indicate an error has
occurred somewhere and may cause the user agent to emit a
warning.</p>
resource are not to be used, must be ignored.</p>

<p>HTTP 204 No Content, and 205 Reset Content responses must be
treated as if they were 200 OK responses with the right MIME type
but no content, and should therefore cause the user agent to refetch
the resource after a delay equal to the reconnection time of the
event source.</p>

<p>Other HTTP response codes in the 2xx range <!--201 Created, 202
Accepted, 203 Non-Authoritative Information, and 206 Partial
Content-->must be treated like HTTP 200 OK responses for the
purposes of reopening event source resources. They are, however,
likely to indicate an error has occurred somewhere and may cause the
user agent to emit a warning.</p>

<p>HTTP 300 Multiple Choices responses should be handled
automatically if possible (treating the responses as if they were
302 Found responses pointing to the appropriate resource), and
Expand Down Expand Up @@ -47156,19 +47157,16 @@ XXX Once we resolve the style="" issue, address these:
Authentication Required should be treated transparently as for any
other subresource.</p>

<p>Any other HTTP response code not listed here should cause the
user agent to stop trying to process this event source.</p> <!--
including: 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>DNS errors must be considered fatal, and cause the user agent to
not open any connection for that event source.</p>
<p>Any other HTTP response code not listed here or network error
(e.g. DNS errors) must be ignored.</p> <!-- including: 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.</p>

Expand Down Expand Up @@ -57655,8 +57653,9 @@ interface <dfn>TimeoutHandler</dfn> {
Stuart Parmenter, Sunava Dutta, Tantek &Ccedil;elik, Terrence Wood,
Thomas Broyer, Thomas O'Connor, Tim Altman, Tim Johansson, Travis
Leithead, Tyler Close, Vladimir Vuki&#x0107;evi&#x0107;, Wakaba,
Wayne Pollock, William Swanson, Yi-An Huang, and &Oslash;istein
E. Andersen, for their useful and substantial comments.</p>
Wayne Pollock, Wellington Fernando de Macedo, William Swanson, Yi-An
Huang, and &Oslash;istein E. Andersen, for their useful and
substantial comments.</p>

<p>Thanks also to everyone who has ever posted about HTML5 to their
blogs, public mailing lists, or forums, including the <a
Expand Down

0 comments on commit 95ca172

Please sign in to comment.