diff options
author | Hiroshi Ichikawa <gimite@gmail.com> | 2011-06-26 10:56:45 +0900 |
---|---|---|
committer | Hiroshi Ichikawa <gimite@gmail.com> | 2011-06-26 10:56:45 +0900 |
commit | 940e435d00ce3e40908f86650f265fbf6ba79a53 (patch) | |
tree | 88e83dc1a656fa374a4bc39a0e8fc2ee7bff7f24 | |
parent | c6b157474f313660edca568ccc76035276e2da14 (diff) | |
download | web-socket-js-940e435d00ce3e40908f86650f265fbf6ba79a53.tar.gz |
Adding HTML/SWF domain issue to 'Troubleshooting' section of README.
-rw-r--r-- | README.md | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -69,13 +69,15 @@ and use Developer Tools (Chrome/Safari) or Firebug (Firefox) to see if console.l 3. Make sure you do NOT open your HTML page as local file e.g. file:///.../sample.html. web-socket-js doesn't work on local file. Open it via Web server e.g. http:///.../sample.html. -4. If you are NOT using web-socket-ruby or em-websocket as your WebSocket server, you need to place Flash socket policy file on your server. See "Flash socket policy file" section below for details. +4. Make sure you host your HTML page and WebSocketMain.swf in the same domain. Otherwise, see "How to host HTML file and SWF file in different domains" section. -5. Check if sample.html bundled with web-socket-js works. +5. If you are NOT using web-socket-ruby or em-websocket as your WebSocket server, you need to place Flash socket policy file on your server. See "Flash socket policy file" section below for details. -6. Make sure the port used for WebSocket (10081 in example above) is not blocked by your server/client's firewall. +6. Check if sample.html bundled with web-socket-js works. -7. Install [debugger version of Flash Player](http://www.adobe.com/support/flashplayer/downloads.html) to see Flash errors. +7. Make sure the port used for WebSocket (10081 in example above) is not blocked by your server/client's firewall. + +8. Install [debugger version of Flash Player](http://www.adobe.com/support/flashplayer/downloads.html) to see Flash errors. ## Supported environments |