commit 2d871a1a4f8e3a3be60d3a11c4842e70ae260c82 Author: David Fifield david@bamsoftware.com Date: Sat Mar 26 14:23:22 2016 -0700
We don't need to worry about the base64 WebSockets.
That's only for very very old Firefox. Even for flash proxy it was only relevant for a short time. --- proxy/websocket.coffee | 1 - 1 file changed, 1 deletion(-)
diff --git a/proxy/websocket.coffee b/proxy/websocket.coffee index e4a9550..94cf274 100644 --- a/proxy/websocket.coffee +++ b/proxy/websocket.coffee @@ -47,7 +47,6 @@ buildUrl = (scheme, host, port, path, params) ->
makeWebsocket = (addr) -> url = buildUrl 'ws', addr.host, addr.port, '/' - # TODO: Do we need to worry about the base64 version? ws = new WebSocket url ### 'User agents can use this as a hint for how to handle incoming binary data: if
tor-commits@lists.torproject.org