- From: poot <cvsmail@w3.org>
- Date: 2011年6月20日 15:59:47 -0400
- To: public-html-diffs@w3.org
- Message-Id: <E1QYkdP-0004UX-16@jay.w3.org>
SSE; hixie: Fix some issues with the recent CORSification of EventSource. (whatwg r6257) http://dev.w3.org/cvsweb/html5/eventsource/Overview.html?r1=1.179&r2=1.180&f=h http://html5.org/tools/web-apps-tracker?from=6256&to=6257 =================================================================== RCS file: /sources/public/html5/eventsource/Overview.html,v retrieving revision 1.179 retrieving revision 1.180 diff -u -d -r1.179 -r1.180 --- Overview.html 17 Jun 2011 19:58:06 -0000 1.179 +++ Overview.html 20 Jun 2011 19:59:36 -0000 1.180 @@ -211,7 +211,7 @@ <h1>Server-Sent Events</h1> - <h2 class="no-num no-toc" id="editor-s-draft-17-june-2011">Editor's Draft 17 June 2011</h2> + <h2 class="no-num no-toc" id="editor-s-draft-20-june-2011">Editor's Draft 20 June 2011</h2> <dl><dt>Latest Published Version:</dt> <dd><a href="http://www.w3.org/TR/eventsource/">http://www.w3.org/TR/eventsource/</a></dd> <dt>Latest Editor's Draft:</dt> @@ -317,7 +317,7 @@ </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> is the W3C working group responsible for this specification's progress along the W3C Recommendation track. - This specification is the 17 June 2011 Editor's Draft. + This specification is the 20 June 2011 Editor's Draft. </p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables @@ -449,12 +449,6 @@ <li><p>Return a new <code><a href="#eventsource">EventSource</a></code> object, and continue these steps in the background (without blocking scripts).</li> - <li><p>If the <span>origin</span> of the resulting <span>absolute - URL</span> is not the <span>same origin</span> as that of the - <span>entry script</span>, then act as if the resource could not be - obtained due to a network error: <a href="#fail-the-connection">fail the connection</a> - and abort these steps.</li> - <li> <p>Do a <span>potentially CORS-enabled fetch</span> of the @@ -528,8 +522,11 @@ source's <a href="#concept-event-stream-last-event-id" title="concept-event-stream-last-event-id">last event ID string</a>, encoded as UTF-8.<p>User agents should use the <code>Cache-Control: no-cache</code> header in requests to bypass any caches for requests of event - sources. User agents should ignore HTTP cache headers in the - response, never caching event sources.<hr><p>As data is received, the <span title="concept-task">tasks</span> + sources. (This header is not a <span title="custom request + headers">custom request header</span>, so the user agent will still + use the CORS <span>simple cross-origin request</span> mechanism.) + User agents should ignore HTTP cache headers in the response, never + caching event sources.<hr><p>As data is received, the <span title="concept-task">tasks</span> queued by the <span>networking task source</span> to handle the data must act as follows.<p>HTTP 200 OK responses with a <span>Content-Type</span> header specifying the type <code><a href="#text-event-stream">text/event-stream</a></code>, either with no
Received on Monday, 20 June 2011 19:59:52 UTC