Hi folks!
I was recently doing some experiments with Server-Sent Events
technology and come to an issue when EventSource url resource is from
a different origin (in my case different subdomain). When this happens
Chrome 13 gives this:
Uncaught Error: SECURITY_ERR: DOM Exception 18
and Firefox 6
On Mon, 05 Sep 2011 10:42:07 +0200, Tomi bosak.to...@gmail.com wrote:
I was recently doing some experiments with Server-Sent Events
technology and come to an issue when EventSource url resource is from
a different origin (in my case different subdomain). When this happens
Chrome 13 gives this:
On Mon, 05 Sep 2011 11:38:11 +0200, Tomi bosak.to...@gmail.com wrote:
So if the current SSE specification is implemented by the browser
vendors, CORS enabled url resource in EventSource should work?
Yes.
Even Opera is going to support CORS in general (as far as I know Opera
doesn't support
Thank you very much Anne for your answers, one more question: is there
a document or some kind of resource where I can see which draft
version of SSE or some HTML5 specification is currently implemented in
Opera?
On 5 September 2011 11:44, Anne van Kesteren ann...@opera.com wrote:
On Mon, 05 Sep
On Mon, 05 Sep 2011 13:05:45 +0200, Tomi bosak.to...@gmail.com wrote:
Thank you very much Anne for your answers, one more question: is there
a document or some kind of resource where I can see which draft
version of SSE or some HTML5 specification is currently implemented in
Opera?
On Tue, 19 Oct 2010 21:24:25 +0200, Nicholas Zakas nza...@yahoo-inc.com
wrote:
IMHO, CORS really needs to be included as part of any implementation so
that this can be used at scale. Otherwise, developers would be forced to
use an iframe/postMessage() mechanism to work around the same origin
In the latest draft of Server-Sent Events, the EventSource object upholds the
same origin policy for event stream resources. Although CORS is mentioned in
the references section, it's not mentioned in the body of the spec, so I was
wondering if this has been brought up before?
The reason I
