[html5] r5401 - [e] (0) Remove redundant requirements. Fixing http://www.w3.org/Bugs/Public/show [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-08-30 11:47:21 -0700 (Mon, 30 Aug 2010)
New Revision: 5401

Modified:
   complete.html
   source
Log:
[e] (0) Remove redundant requirements.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10127

Modified: complete.html
===================================================================
--- complete.html	2010-08-30 18:38:38 UTC (rev 5400)
+++ complete.html	2010-08-30 18:47:21 UTC (rev 5401)
@@ -72532,26 +72532,17 @@
   are, however, likely to indicate an error has occurred somewhere and
   may cause the user agent to emit a warning.</p>
 
-  <p>HTTP 301 Moved Permanently responses must cause the user agent to
-  reconnect using the new server specified URL instead of the
-  previously specified URL for all subsequent requests for this event
-  source. (It doesn't affect other <code><a href=#eventsource>EventSource</a></code> objects
-  with the same URL unless they also receive 301 responses, and it
-  doesn't affect future sessions, e.g. if the page is reloaded.)</p>
-
-  <p>HTTP 302 Found, 303 See Other, and 307 Temporary Redirect
-  responses must cause the user agent to connect to the new
-  server-specified URL, but if the user agent needs to again request
-  the resource at a later point for the same event source, it must
-  return to the previously specified URL for this event source.</p>
-
-  <p class=note>The Origin specification also introduces some
-  relevant requirements when dealing with redirects. <a href=#refsORIGIN>[ORIGIN]</a></p>
-
   <p>HTTP 305 Use Proxy, HTTP 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
+  307 Temporary Redirect responses are handled by the <a href=#fetch title=fetch>fetching</a> algorithm. In the case of 301
+  redirects, the user agent must also remember the new URL so that
+  subsequent requests for this 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>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

Modified: source
===================================================================
--- source	2010-08-30 18:38:38 UTC (rev 5400)
+++ source	2010-08-30 18:47:21 UTC (rev 5401)
@@ -81598,27 +81598,18 @@
   are, however, likely to indicate an error has occurred somewhere and
   may cause the user agent to emit a warning.</p>
 
-  <p>HTTP 301 Moved Permanently responses must cause the user agent to
-  reconnect using the new server specified URL instead of the
-  previously specified URL for all subsequent requests for this event
-  source. (It doesn't affect other <code>EventSource</code> objects
-  with the same URL unless they also receive 301 responses, and it
-  doesn't affect future sessions, e.g. if the page is reloaded.)</p>
-
-  <p>HTTP 302 Found, 303 See Other, and 307 Temporary Redirect
-  responses must cause the user agent to connect to the new
-  server-specified URL, but if the user agent needs to again request
-  the resource at a later point for the same event source, it must
-  return to the previously specified URL for this event source.</p>
-
-  <p class="note">The Origin specification also introduces some
-  relevant requirements when dealing with redirects. <a
-  href="#refsORIGIN">[ORIGIN]</a></p>
-
   <p>HTTP 305 Use Proxy, HTTP 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
+  307 Temporary Redirect responses are handled by the <span
+  title="fetch">fetching</span> algorithm. In the case of 301
+  redirects, the user agent must also remember the new URL so that
+  subsequent requests for this resource for this
+  <code>EventSource</code> object start with the URL given for the
+  last 301 seen for requests for this object.</p>
+
   <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