Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox can't establish a connection to the server at - HTML5 Server sent events

more options

When trying to implement html5 server sent event forefox throws the following error in console, it works fine in Google Chrome

My Web Page: http://apex.oracle.com/pls/apex/f?p=1983:6

Error:

==

PM Error: Firefox can't establish a connection to the server at http://apex.oracle.com/pls/apex/f?p=1983:6:0:APPLICATION_PROCESS=SSE. Source File: http://apex.oracle.com/pls/apex/f?p=1983:6 Line: 30

When trying to implement html5 server sent event forefox throws the following error in console, it works fine in Google Chrome My Web Page: http://apex.oracle.com/pls/apex/f?p=1983:6 Error: ====== PM Error: Firefox can't establish a connection to the server at http://apex.oracle.com/pls/apex/f?p=1983:6:0:APPLICATION_PROCESS=SSE. Source File: http://apex.oracle.com/pls/apex/f?p=1983:6 Line: 30

All Replies (1)

more options

I get a similar error on the MDN demo page: https://developer.mozilla.org/samples/sse/

As another test, I uploaded the Friends Timeline demo from Mozilla's Web o' Wonder repository to two different web servers. On one server, the messages appear individually as designed. On a second, they are batched together and sent approximately every 45 seconds (the PHP flush doesn't seem to work).

http://www.jeffersonscher.com/forumshots/friends_timeline/
http://dev.jeffersonscher.com/php/friends_timeline/

One thing that might be significant is the content-type of the event source document. In the request, Firefox includes this HTTP header:

Accept: text/event-stream

In the Oracle case, the Fiddler proxy shows the response body contains this string, which looks promising:

data: Server Time: 28-OCT-2012 18:39:34<br><b>Random Number from server: </b>4

However, there is no content-type header on the response so that might be why Firefox is declaring it a fail.

In the MDN demo, for some reason the content-type is text/plain.

Of the 3 examples, only the Friends Timeline demo seems to be returning the content type text/event-stream as required by the request.