aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2008-01-07 18:54:55 +0000
committerNick Mathewson <nickm@torproject.org>2008-01-07 18:54:55 +0000
commitdd35fe59c4ab562de32288cd984adeac2e931bb6 (patch)
tree582cfafacd09bcaac6fad41d14a80e5dd0e819bd /doc
parenta63eb68fe1546b7e1bebfa192b8ef0bdcc4c6980 (diff)
downloadtor-dd35fe59c4ab562de32288cd984adeac2e931bb6.tar
tor-dd35fe59c4ab562de32288cd984adeac2e931bb6.tar.gz
r17499@catbus: nickm | 2008-01-07 13:39:46 -0500
Bugfix on fix for 557: Make values containing special characters work right with getconf, setconf, and saveconf. Document this in control-spec.txt svn:r13056
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/control-spec.txt7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index 2e31be13d..da4157ac5 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -139,7 +139,8 @@ $Id$
Change the value of one or more configuration variables. The syntax is:
- "SETCONF" 1*(SP keyword ["=" String]) CRLF
+ "SETCONF" 1*(SP keyword ["=" value]) CRLF
+ value = String / QuotedString
Tor behaves as though it had just read each of the key-value pairs
from its configuration file. Keywords with no corresponding values have
@@ -184,6 +185,10 @@ $Id$
empty string, Tor may reply with a reply line of the form:
250 keyword
+ Value may be a raw value or a quoted string. Tor will try to use
+ unquoted values except when the value could be misinterpreted through
+ not being quoted.
+
If some of the listed keywords can't be found, Tor replies with a
"552 unknown configuration keyword" message.