You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier today I needed to test some changes in IE8 and really did not want to give up LiveReload.
I was able to glue https://github.com/gimite/web-socket-js together with LiveReload...and it worked surprisingly well. I had to run a separate websocket policy server (and add the necessary JS/SWF to the page from web-socket-js) in order to get it working, though. Great explanation of the problem at http://www.lightsphere.com/dev/articles/flash_socket_policy.html - basically, Flash will send <policy-file-request/> as a string to port 843 and then to the websocket port. It expects a policy in return such as:
Earlier today I needed to test some changes in IE8 and really did not want to give up LiveReload.
I was able to glue https://github.com/gimite/web-socket-js together with LiveReload...and it worked surprisingly well. I had to run a separate websocket policy server (and add the necessary JS/SWF to the page from web-socket-js) in order to get it working, though. Great explanation of the problem at http://www.lightsphere.com/dev/articles/flash_socket_policy.html - basically, Flash will send
<policy-file-request/>
as a string to port 843 and then to the websocket port. It expects a policy in return such as:At that point this workaround works more or less as a real WebSocket does - enough for LiveReload to function, at least for me. :)
There's actually already an implementation of a Flash policy server in node.js if that helps: https://github.com/3rd-Eden/FlashPolicyFileServer
Thanks for saving me hours of jamming on the F5 key!
The text was updated successfully, but these errors were encountered: