Firefox 3.6.3 problem - Githubissues

gimite / web-socket-js

HTML5 Web Socket implementation powered by Flash

BSD 3-Clause "New" or "Revised" License

2.73k stars 488 forks source link

Firefox 3.6.3 problem #11

Closed etm closed 14 years ago

etm commented 14 years ago

Installed latest web-socket-ruby, started on localhost
copied all files in web-socket-js to /var/www/web-socket.js/, apache running on localhost
accessing sample.html with chromium, everything is fine
accessing sample.html, nothing happens * webSocketContainer with swf is inserted * no output on firebug console \ no onopen is printed

gimite commented 14 years ago

Hmm no idea... Some hints to debug:

Make sure Flash Player is installed and works normally (also check version of Flash Player).
Try installing debug version of Flash Player as described in "How to debug" section of README.txt
Insert console.log() in various location in web_socket.js to see where it stops execution.

gimite commented 14 years ago

Also please make sure you don't provide anything at port 843. If you already provide Flash socket policy file there, you must allow access to 10081 there.

etm commented 14 years ago

1) all needed files are accessible an loaded (apache log) 2) http://localhost:843/ yields,

which should be fine. 3) Flash player is installed and fine: Shockwave Flash 10.0 r42

i will try inserting console.log and then install flash debug player next.

etm commented 14 years ago

p.s. github stripped out the stars between the apostrophes for allow-access-from.

gimite commented 14 years ago

Flash socket policy file at port 843 must be provided as raw TCP response, not with HTTP. See http://www.lightsphere.com/dev/articles/flash_socket_policy.html for details. If you don't use Flash socket anywhere else in your host (anyway it should not work right now), easy solution is to stop providing the policy file at port 843, so that web-socket-ruby handles it itself. Note that you should stop listening at port 843, not returning HTTP response 404.

etm commented 14 years ago

Okay, that was the problem, thanks for your help. Kudos, web-socket-js is a great intermediate solution.

afshinm commented 14 years ago

Hi,

I'm using websocket.js and it worked good in Chrome but in Firefox and IE, WebSocket object created but it not connected to server ...

When i start FireBug, i see some errors:

[WebSocket] cannot connect to Web Socket server at ws://localhost:12345/ (SecurityError) make sure the server is running and Flash socket policy file is correctly placed webSocketError(Object { name="message"})web_socket.js (line 311) [Break on this error] console.error(decodeURIComponent(message));\n

Whats the problem?

Thanks.