WebSockets Disconnected for Firefox 4
by Dylan SchiemannDecember 7th, 2010Per the disable and/or remove WebSockets for gecko 2.0 due to security problems discussion on Bugzilla, and the discussion around security of WebSockets, Firefox 4 is disabling WebSockets by default. A user may enable them via a preference, but they will not be enabled in a final release until the protocol is updated to use a more secure CONNECT-based handshake.
It’s a serious security issue with WebSockets and proxies, so expect a change in the protocol asap to fix this. Unfortunately, this will not happen in time for the release date of Firefox 4.











December 7th, 2010 at 3:39 pm
[...] Firefox 4 beta (Firefox 4 WebSockets will be disabled by default) [...]
December 7th, 2010 at 8:25 pm
I think Opera is disabling as well, and RIM is holding off on enabling it.
December 8th, 2010 at 11:58 am
Chris Blizzard from mozilla has additional details today: http://www.0xdeadbeef.com/weblog/2010/12/disabling-websockets-for-firefox-4/
@Steven, I thought it was already enabled in BB6?
January 3rd, 2011 at 12:02 am
[...] arrival of WebSockets in WebKit-based browsers, and expected in Firefox 4.x and Internet Explorer 9 once the next WebSockets specification draft is completed, and with Comet techniques used by many of the world’s most popular sites, Comet has arrived [...]
February 8th, 2011 at 7:34 am
[...] WebSocket transport has been disabled by default on the client-side until the specification is refined and implemented to address the current proxy [...]