|
@@ -150,6 +150,7 @@ Tor Rendezvous Spec
|
|
|
1.4. Bob's OP advertises his server descriptor
|
|
|
|
|
|
Bob's OP opens a stream to each directory server's directory port via Tor.
|
|
|
+ (He may re-use old circuits for this.)
|
|
|
Over this stream, Bob's OP makes an HTTP 'POST' request, to the URL
|
|
|
'/rendezvous/publish' (relative to the directory server's root),
|
|
|
containing as its body Bob's service descriptor. Upon receiving a
|
|
@@ -188,9 +189,10 @@ Tor Rendezvous Spec
|
|
|
|
|
|
Alice opens a stream to a directory server via Tor, and makes an HTTP GET
|
|
|
request for the document '/rendezvous/<y>', where '<y> is replaced with the
|
|
|
- encoding of Bob's public key as described above. The directory replies
|
|
|
- with a 404 HTTP response if it does not recognize <y>, and otherwise
|
|
|
- returns Bob's most recently uploaded service descriptor.
|
|
|
+ encoding of Bob's public key as described above. (She may re-use old
|
|
|
+ circuits for this.) The directory replies with a 404 HTTP response if
|
|
|
+ it does not recognize <y>, and otherwise returns Bob's most recently
|
|
|
+ uploaded service descriptor.
|
|
|
|
|
|
If Alice's OP receives a 404 response, it tries the other directory
|
|
|
servers, and only fails the lookup if none recognizes the public key hash.
|