[tor-commits] [torspec/master] Clarify about empty GETCONF request
nickm at torproject.org
nickm at torproject.org
Wed Feb 5 13:53:13 UTC 2020
commit 1f4ae3d62f695129ee363ec69a115413e25a6c20
Author: rl1987 <rl1987 at sdf.lonestar.org>
Date: Mon Feb 3 16:56:53 2020 +0800
Clarify about empty GETCONF request
---
control-spec.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/control-spec.txt b/control-spec.txt
index cdd1af3..64a70fc 100644
--- a/control-spec.txt
+++ b/control-spec.txt
@@ -307,7 +307,8 @@
3.3. GETCONF
- Request the value of a configuration variable(s). The syntax is:
+ Request the value of zero or more configuration variable(s).
+ The syntax is:
"GETCONF" *(SP keyword) CRLF
@@ -332,6 +333,8 @@
If an option appears multiple times in the configuration, all of its
key-value pairs are returned in order.
+ If no keywords were provided, Tor responds with "250 OK" message.
+
Some options are context-sensitive, and depend on other options with
different keywords. These cannot be fetched directly. Currently there
is only one such option: clients should use the "HiddenServiceOptions"
More information about the tor-commits
mailing list