summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2005-06-19 23:22:34 +0000
committerNick Mathewson <nickm@torproject.org>2005-06-19 23:22:34 +0000
commite376e6cc0702f32a004e2c875a709c42eaeb19ed (patch)
tree1d9477f2835b2638ba0077b148d5c38967acf295
parentd2d934cc10b089336de57ab3dde97e0c173a9fc2 (diff)
downloadtor-e376e6cc0702f32a004e2c875a709c42eaeb19ed.tar.gz
tor-e376e6cc0702f32a004e2c875a709c42eaeb19ed.zip
note GETCONF default feature in spec
svn:r4463
-rw-r--r--doc/control-spec.txt12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index c63e96c8d7..81d1cd7776 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -138,6 +138,9 @@ $Id$
If all of the listed keywords exist in the Tor configuration, Tor replies
with a series of reply lines of the form:
250 keyword=value
+ If any option is set to a 'default' value semantically different from an
+ empty string, Tor may reply with a reply line of the form:
+ 250 keyword
If some of the listed keywords can't be found, Tor replies with a
"552 unknown configuration keyword" message.
@@ -520,6 +523,15 @@ about dns resolves, etc, so the controller can keep synced. -RD]
S: 650 CIRC 1000 EXTENDED moria1,moria2
S: 250 ORPORT=0
+ Clients SHOULD tolerate more arguments in an asynchonous reply than
+ expected, and SHOULD tolerate more lines in an asynchronous reply than
+ expected. For instance, a client that expects a CIRC message like:
+ 650 CIRC 1000 EXTENDED moria1,moria2
+ should tolerate:
+ 650+CIRC 1000 EXTENDED moria1,moria2 0xBEEF
+ 650-EXTRAMAGIC=99
+ 650 ANONYMITY=high
+
4.1.1 Circuit status changed
The syntax is: