mirror of
https://github.com/torproject/torspec.git
synced 2025-02-14 05:28:56 +00:00
Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
so we can exit from the middle of the circuit. svn:r10056
This commit is contained in:
parent
aa2bc0c5f7
commit
e140141614
@ -535,7 +535,7 @@ $Id$
|
||||
3.13. ATTACHSTREAM
|
||||
|
||||
Sent from the client to the server. The syntax is:
|
||||
"ATTACHSTREAM" SP StreamID SP CircuitID CRLF
|
||||
"ATTACHSTREAM" SP StreamID SP CircuitID ["HOP=" HopNum] CRLF
|
||||
|
||||
This message informs the server that the specified stream should be
|
||||
associated with the specified circuit. Each stream may be associated with
|
||||
@ -547,6 +547,9 @@ $Id$
|
||||
If the circuit ID is 0, responsibility for attaching the given stream is
|
||||
returned to Tor.
|
||||
|
||||
If HOP=HopNum is specified, Tor will choose the HopNumth hop in the
|
||||
circuit as the exit node, rather than the last node in the circuit.
|
||||
|
||||
Tor responds with "250 OK" if it can attach the stream, 552 if the circuit
|
||||
or stream didn't exist, or 551 if the stream couldn't be attached for
|
||||
another reason.
|
||||
|
Loading…
x
Reference in New Issue
Block a user