Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Consistency in editorial style.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=15956
Affected topics: Server-Sent Events

git-svn-id: http://svn.whatwg.org/webapps@6989 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Feb 11, 2012
1 parent 856ed5a commit 8aba106
Show file tree
Hide file tree
Showing 3 changed files with 39 additions and 42 deletions.
27 changes: 13 additions & 14 deletions complete.html
Expand Up @@ -77135,11 +77135,11 @@ <h4 id=processing-model-5><span class=secno>10.2.3 </span>Processing model</h4>
<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
<p>HTTP 305 Use Proxy, 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
other subresource.</p>

<p>HTTP 301 Moved Permanently, HTTP 302 Found, 303 See Other, and
<p>HTTP 301 Moved Permanently, 302 Found, 303 See Other, and
307 Temporary Redirect responses are handled by the <a href=#fetch title=fetch>fetching</a> and CORS algorithms. In the case of
301 redirects, the user agent must also remember the new URL so that
subsequent requests for this resource for this
Expand All @@ -77150,18 +77150,17 @@ <h4 id=processing-model-5><span class=secno>10.2.3 </span>Processing model</h4>
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 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 -->
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, 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>

Expand Down
27 changes: 13 additions & 14 deletions index
Expand Up @@ -77135,11 +77135,11 @@ dictionary <dfn id=eventsourceinit>EventSourceInit</dfn> {
<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
<p>HTTP 305 Use Proxy, 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
other subresource.</p>

<p>HTTP 301 Moved Permanently, HTTP 302 Found, 303 See Other, and
<p>HTTP 301 Moved Permanently, 302 Found, 303 See Other, and
307 Temporary Redirect responses are handled by the <a href=#fetch title=fetch>fetching</a> and CORS algorithms. In the case of
301 redirects, the user agent must also remember the new URL so that
subsequent requests for this resource for this
Expand All @@ -77150,18 +77150,17 @@ dictionary <dfn id=eventsourceinit>EventSourceInit</dfn> {
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 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 -->
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, 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>

Expand Down
27 changes: 13 additions & 14 deletions source
Expand Up @@ -89457,11 +89457,11 @@ dictionary <dfn>EventSourceInit</dfn> {
<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
<p>HTTP 305 Use Proxy, 401 Unauthorized, and 407 Proxy
Authentication Required should be treated transparently as for any
other subresource.</p>

<p>HTTP 301 Moved Permanently, HTTP 302 Found, 303 See Other, and
<p>HTTP 301 Moved Permanently, 302 Found, 303 See Other, and
307 Temporary Redirect responses are handled by the <span
title="fetch">fetching</span> and CORS algorithms. In the case of
301 redirects, the user agent must also remember the new URL so that
Expand All @@ -89473,18 +89473,17 @@ dictionary <dfn>EventSourceInit</dfn> {
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 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 -->
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, 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>

Expand Down

0 comments on commit 8aba106

Please sign in to comment.