WebSockets seem totally broken by Firefox SOCKS settings
http://html5demos.com/web-socket is failing on both TBB 2.2.x and 2.3.x. I also tested a Vanilla FF14 with SOCKS proxy settings, and the socket also breaks there, too.
This is thus probably an upstream Firefox bug. We should at least file a bugzilla bug and bring it to someone's attention, I guess.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Mike Perry added component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac priority::medium in Legacy / Trac resolution::invalid in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tbb-bounty in Legacy / Trac tbb-firefox-patch in Legacy / Trac tbb-usability-website in Legacy / Trac type::defect in Legacy / Trac labels
added component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac priority::medium in Legacy / Trac resolution::invalid in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac tbb-bounty in Legacy / Trac tbb-firefox-patch in Legacy / Trac tbb-usability-website in Legacy / Trac type::defect in Legacy / Trac labels
- Author Reporter
Trac:
Keywords: N/A deleted, tbb-usability-website added - Author Reporter
Trac:
Keywords: N/A deleted, tbb-bounty added I cannot get http://html5demos.com/web-socket to work in vanilla Firefox 17 even without SOCKS (it does work in Chrome 16). The demo at http://www.websocket.org/echo.html does work in Firefox 17 both with and without SOCKS configured.
Trac:
Keywords: N/A deleted, tbb-firefox-patch addedTrac:
Owner: mikeperry to tbb-team
Component: Firefox Patch Issues to Tor BrowserReplying to [ticket:5292#comment:6 mikeperry] (from ticket:5292):
http://html5demos.com/web-socket Application Error (Test is dead) http://www.websocket.org/ Works This error appears in the FF error console:
Error: Firefox can't establish a connection to the server at ws://node.remysharp.com:8001/. Source File: http://html5demos.com/web-socket Line: 54 }}}
This error appears for those webpages which use swf (Adobe Flash) instead of JS for WebSocket, and it's quite confusing, yeah. Or when JS is used by https://webirc.oftc.net ;) {{{ Torbutton INFO: tor SOCKS: https://webirc.oftc.net:8443/socket.io/?EIO=3&transport=polling&t=1472662463500-5&sid=7R-gdaxz9kejlJv6ACGE via oftc.net:4f53916b35aff4720ecd401c5e1302e2 Firefox can't establish a connection to the server at wss://webirc.oftc.net:8443/socket.io/?EIO=3&transport=websocket&sid=7R-gdaxz9kejlJv6ACGE. qui-0cc18125cbfe7c291eca.js:8132:15 The connection to wss://webirc.oftc.net:8443/socket.io/?EIO=3&transport=websocket&sid=7R-gdaxz9kejlJv6ACGE was interrupted while the page was loading. qui-0cc18125cbfe7c291eca.js:8132:15 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-monitor.js:84:0
Or by https://storm.torproject.org
Firefox can't establish a connection to the server at wss://storm.torproject.org/sockjs/435/ceuw1mnv/websocket. 7e8aa475d2075bbe5de6d8cac1f43c6b5ce296a1.js:53:17714
Nevertheless, http://websocketstest.com is everything you need for testing. Maybe, there are some issues with WebSocket for separate tickets, but according to the Summary and the Description this ticket can be closed. **Trac**: **Resolution**: *N/A* **to** invalid **Reviewer**: *N/A* **to** *N/A* **Sponsor**: *N/A* **to** *N/A* **Severity**: *N/A* **to** Normal **Status**: new **to** closed
- Trac closed
closed
- Trac moved from legacy/trac#6577 (moved)
moved from legacy/trac#6577 (moved)