Lines Matching full:your
9 - If your server already provides socket policy file at port 843, modify the file to allow access to port 10081. Otherwise you can skip this step. See below for details.
10 - Publish the web-socket-js directory with your Web server (e.g. put it in ~/public_html).
12 - Open sample.html in your browser.
24 -- It's likely an issue of your code or the server. Debug your code as usual e.g. using console.log.
27 - It works on both Chrome and Firefox, but it doesn't work on your browser:
28 -- Check "Supported environment" section below. Your browser may not be supported by web-socket-js.
30 2. Add this line before your code:
34 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.
36 4. If you are NOT using web-socket-ruby as your WebSocket server, you need to place Flash socket policy file on your server. See "Flash socket policy file" section below for details.
40 6. Make sure the port used for WebSocket (10081 in example above) is not blocked by your server/client's firewall.
57 This implementation uses Flash's socket, which means that your server must provide Flash socket policy file to declare the server accepts connections from Flash.
75 Note that it's technically possible that client sends arbitrary string as Cookie and any other headers (by modifying this library for example) once you place Flash socket policy file in your server. So don't trust Cookie and other headers if you allow connection from untrusted origin.
91 WARNING: If you use the method below, HTML files in ANY domains can send arbitrary TCP data to your WebSocket server, regardless of configuration in Flash socket policy file. Arbitrary TCP data means that they can even fake request headers including Origin and Cookie.
94 - Put WebSocketMainInsecure.swf on your server, instead of WebSocketMain.swf.
95 - In JavaScript, set WEB_SOCKET_SWF_LOCATION to URL of your WebSocketMainInsecure.swf.
