Re:WebSockets RFC is now official
by aaronblohowiak on Sunday December 11, 2011 @07:17PM
(#3341611)
Yay! Looks like they fixed it. Now, it looks like it is a normal upgrade request so proxies, et al, should play nice. Yaaay!
[ Parent
| on HN ]
Many proxies deployed today won't understand the upgrade header and in the case of an explicit proxy config will ignore the CONNECT operation if performed on 80 (rather than 443).
WebSockets works best over SSL.
Yep, they undid the crazy 8 bytes of body that wasn't declared by content-length, back in hixie-76. The current protocols play nicely with HTTP aware proxies now.
They introduced plenty of other crazy things.. but at least it works with proxies.
I'm not to happy with this change though.
At least with hixie-76, connections would fail to connect if the intermediate proxies are not understanding WebSockets. Now, your connection will succeed, both client and server will believe they can successfully communicate, but communication will not work and die a slow timeout. Not very reliable, is it ?
Re:WebSockets RFC is now official
by maximusprime on Monday December 12, 2011 @07:24AM
(#3343328)
* try websocket
* on failure, fallback to comet
It's fairly easy to implement.