Changes between Initial Version and Version 1 of Ticket #19910, comment 15


Ignore:
Timestamp:
Jan 30, 2018, 3:02:27 AM (20 months ago)
Author:
arthuredelstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19910, comment 15

    initial v1  
    88  2. The SOCKS client sends a SOCKS CONNECT command
    99  3. The proxy immediately returns a spoofed SOCKS CONNECTED notification to the SOCKS client, and the proxy also sends a BEGIN cell to the Exit.
    10   4. The SOCKS client sends some data to the OP (the GET request, for example).
    11   5. The OP sends a DATA cell to the Exit
     10  4. The SOCKS client sends some data to the proxy (the GET request, for example).
     11  5. The proxy sends a DATA cell to the Exit
    1212
    1313This arrangement doesn't require any modification to the browser's SOCKS implementation, but it means we don't wait for the Exit to respond with CONNECTED before asking the SOCKS client to send its first data. Basically we put the "optimism" in the proxy instead of the browser. That's nice because then (1) we will get a speedup to all ordinary SOCKS clients and (2) we're patching code controlled by Tor Project.