Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #5382

Closed
Open
Created Mar 13, 2012 by David Fifield@dcf

Port SWF flash proxy to JavaScript

It's impolite to ask volunteers to run Adobe Flash; also it complicates development, deployment, and testing. It ought to be possible to do everything the Flash badge does in JavaScript (with the exception of the deprecated RTMFP transport).

flash.net.URLLoader becomes XMLHttpRequest. flash.net.Socket becomes WebSocket. Rather than having to run a crossdomain policy server, endpoints will have to understand the WebSocket header. On the Tor relay side, we may run a WebSocket proxy such as https://github.com/kanaka/websockify. On the client side, it should be built into the connector, just as the connector now has a crossdomain server.

This development is happening in https://gitweb.torproject.org/flashproxy.git/shortlog/refs/heads/js.

  • WebSocket network protocol: http://tools.ietf.org/html/rfc6455.
  • WebSocket programmer API: http://dev.w3.org/html5/websockets/.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking