Permalink
Browse files

[] (0) Mark the semantics of cross-origin event sources as work-in-pr…

…ogress.

git-svn-id: http://svn.whatwg.org/webapps@2851 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Feb 23, 2009
1 parent 2fba31f commit 76d1c9e08c6814c6b23352c53b17d795d33ba48a
Showing with 16 additions and 21 deletions.
  1. +8 −10 index
  2. +8 −11 source
View
18 index
@@ -45761,15 +45761,14 @@ XXX Once we resolve the style="" issue, address these:
be included with the request, whose value is the value of the event
source's last event ID string.</p>
- <p>For connections to domains other than <a href="#the-document's-domain">the document's
- domain</a>, the semantics of the Access-Control HTTP header must
- be followed. <a href=#refsACCESSCONTROL>[ACCESSCONTROL]</a> <!--
- XXX define this better once that spec is more stable -->
+ <p class=XXX>Cross-origin loads are expected to follow the
+ Access-Control semantics of CORS; without this header, they are
+ expected to fail as if the site was down.</p>
<p>HTTP 200 OK responses with a <a href=#content-type-0>Content-Type</a> header
- specifying the type <code>text/event-stream</code> that are either
- from <a href="#the-document's-domain">the document's domain</a> or explicitly allowed by the
- Access-Control HTTP headers must be processed line by line <a href=#event-stream-interpretation>as described below</a>.</p>
+ specifying the type <code>text/event-stream</code> must be processed
+ line by line <a href=#event-stream-interpretation>as described
+ below</a>.</p>
<p>For the purposes of such successfully opened event streams only,
user agents should ignore HTTP cache headers, and instead assume
@@ -45783,9 +45782,8 @@ XXX Once we resolve the style="" issue, address these:
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.</p>
+ than <code>text/event-stream</code> (or some other supported type)
+ 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
View
19 source
@@ -52262,16 +52262,14 @@ XXX Once we resolve the style="" issue, address these:
be included with the request, whose value is the value of the event
source's last event ID string.</p>
- <p>For connections to domains other than <span>the document's
- domain</span>, the semantics of the Access-Control HTTP header must
- be followed. <a href="#refsACCESSCONTROL">[ACCESSCONTROL]</a> <!--
- XXX define this better once that spec is more stable -->
+ <p class="XXX">Cross-origin loads are expected to follow the
+ Access-Control semantics of CORS; without this header, they are
+ expected to fail as if the site was down.</p>
<p>HTTP 200 OK responses with a <span>Content-Type</span> header
- specifying the type <code>text/event-stream</code> that are either
- from <span>the document's domain</span> or explicitly allowed by the
- Access-Control HTTP headers must be processed line by line <a
- href="#event-stream-interpretation">as described below</a>.</p>
+ specifying the type <code>text/event-stream</code> must be processed
+ line by line <a href="#event-stream-interpretation">as described
+ below</a>.</p>
<p>For the purposes of such successfully opened event streams only,
user agents should ignore HTTP cache headers, and instead assume
@@ -52285,9 +52283,8 @@ XXX Once we resolve the style="" issue, address these:
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.</p>
+ than <code>text/event-stream</code> (or some other supported type)
+ 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

0 comments on commit 76d1c9e

Please sign in to comment.