[html5] r6989 - [e] (0) Consistency in editorial style. Fixing https://www.w3.org/Bugs/Public/sh [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sat Feb 11 10:45:13 PST 2012
Author: ianh
Date: 2012-02-11 10:45:11 -0800 (Sat, 11 Feb 2012)
New Revision: 6989
Modified:
complete.html
index
source
Log:
[e] (0) Consistency in editorial style.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=15956
Affected topics: Server-Sent Events
Modified: complete.html
===================================================================
--- complete.html 2012-02-11 18:42:56 UTC (rev 6988)
+++ complete.html 2012-02-11 18:45:11 UTC (rev 6989)
@@ -77135,11 +77135,11 @@
<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
@@ -77150,18 +77150,17 @@
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>
Modified: index
===================================================================
--- index 2012-02-11 18:42:56 UTC (rev 6988)
+++ index 2012-02-11 18:45:11 UTC (rev 6989)
@@ -77135,11 +77135,11 @@
<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
@@ -77150,18 +77150,17 @@
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>
Modified: source
===================================================================
--- source 2012-02-11 18:42:56 UTC (rev 6988)
+++ source 2012-02-11 18:45:11 UTC (rev 6989)
@@ -89457,11 +89457,11 @@
<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
@@ -89473,18 +89473,17 @@
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>
More information about the Commit-Watchers
mailing list