[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9349 [Flashproxy]: flashproxy facilitator: Allow clients to specify transports
#9349: flashproxy facilitator: Allow clients to specify transports
----------------------------+-------------------
Reporter: asn | Owner: dcf
Type: task | Status: new
Priority: normal | Milestone:
Component: Flashproxy | Version:
Resolution: | Keywords:
Actual Points: | Parent ID: #7167
Points: |
----------------------------+-------------------
Comment (by dcf):
Replying to [comment:19 asn]:
> For what's it's worth, latest branches at this point are:
> Facilitator: `bug9349_server_side_draft`
> flashproxy-client: `bug9349_client_side`
> flashproxy: `bug9349_proxy_second_take`
I merged bug9349_proxy_second_take. As [comment:25 Ximin observes], we'll
also need something that walks the query string keys of the facilitator
response, to look for `client-<transport>` keys, somewhere around
[https://gitweb.torproject.org/flashproxy.git/blob/0eccc984c50bae6736b58a2e75ed3af8e41a7b1e:/proxy/flashproxy.js#l628
here].
I created a copy of bug9349_server_side_draft at
https://git.torproject.org/user/dcf/flashproxy.git branch bug9349_server,
where I'll be merging and committing my own changes.
I'm going to set up a public test facilitator where we can test the server
branch.
I'm not going to worry too much about the client side for now; the only
thing we need is a modified registration, and that's easy to temporarily
hack in when we have a running facilitator. I think it will be easy to
merge at that point.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9349#comment:30>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs