On Thu, 16 Jul 2009, Amos Jeffries wrote: > > > > What solution would you recommend for such a case? > > a) Getting a dedicated WebSocket port assigned.
The plan is to ask for ports 81 and 815. > * You and the client needing it have an argument to get that port opened > through the firewall. > * Squid and other proxies can be altered to allow CONNECT through to safe > defined ports (80 is not one). Or to do the WebSocket upgrade itself. On the long term, that is the expected solution, yes. It doesn't work on the short term, though. > b) accepting that the network being traversed is screwed beyond > redemption by its own policy or admin. That's not really a solution. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
