aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-10-13 14:37:40 -0400
committerNick Mathewson <nickm@torproject.org>2020-10-13 14:38:32 -0400
commit42a5e652cb9dc9818abd63d93fd51e908f2c56a4 (patch)
treefa777792bec97c4fcccba8fa36eb6b2596ad7ad7 /doc
parentac311a38ec62e17868b484b8ace069d171c7506d (diff)
downloadtor-42a5e652cb9dc9818abd63d93fd51e908f2c56a4.tar.gz
tor-42a5e652cb9dc9818abd63d93fd51e908f2c56a4.zip
Make OptimisticData always-on.
We've been using it for years, and it seems to work just fine. This patch removes the option and its network parameter. Part of #40139
Diffstat (limited to 'doc')
-rw-r--r--doc/man/tor.1.txt9
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt
index cd53d5ea26..0e54fe9e0f 100644
--- a/doc/man/tor.1.txt
+++ b/doc/man/tor.1.txt
@@ -1314,15 +1314,6 @@ The following options are useful only for clients (that is, if
Every NUM seconds consider whether to build a new circuit. (Default: 30
seconds)
-[[OptimisticData]] **OptimisticData** **0**|**1**|**auto**::
- When this option is set, and Tor is using an exit node that supports
- the feature, it will try optimistically to send data to the exit node
- without waiting for the exit node to report whether the connection
- succeeded. This can save a round-trip time for protocols like HTTP
- where the client talks first. If OptimisticData is set to **auto**,
- Tor will look at the UseOptimisticData parameter in the networkstatus.
- (Default: auto)
-
// These are out of order because they logically belong together
[[PathBiasCircThreshold]] **PathBiasCircThreshold** __NUM__ +