aboutsummaryrefslogtreecommitdiff
path: root/socks-extensions.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-07-20 11:08:09 -0400
committerNick Mathewson <nickm@torproject.org>2011-07-20 11:08:09 -0400
commit4212db3cb902a368199d96b3483f4ce15ce4cfed (patch)
tree6bd2f666938156892e31cfc106072c8c0db8a0fb /socks-extensions.txt
parent6a2136dac7cbe9c8cff7965fb6050207c971a9fc (diff)
downloadtorspec-4212db3cb902a368199d96b3483f4ce15ce4cfed.tar.gz
torspec-4212db3cb902a368199d96b3483f4ce15ce4cfed.zip
Spec changes for proposal 181 (client-side optimistic data)
Diffstat (limited to 'socks-extensions.txt')
-rw-r--r--socks-extensions.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/socks-extensions.txt b/socks-extensions.txt
index f587d9c..b9f070a 100644
--- a/socks-extensions.txt
+++ b/socks-extensions.txt
@@ -75,6 +75,19 @@ Tor's extensions to the SOCKS protocol
misconfigured. This is helpful for the many users who mistakenly try to
use Tor as an HTTP proxy instead of a SOCKS proxy.
+5. Optimistic data
+
+ Tor allows SOCKS clients to send connection data before Tor has sent a
+ SOCKS response. When using an exit node that supports "optimistic data",
+ Tor will send such data to the server without waiting to see whether the
+ connection attempt succeeds. This behavior can save a single round-trip
+ time when starting connections with a protocol where the client speaks
+ first (like HTTP). Clients that do this must be ready to hear that
+ their connection has succeeded or failed _after_ they have sent the
+ data.
+
+
+
References:
[1] http://archive.socks.permeo.com/protocol/socks4.protocol
[2] http://archive.socks.permeo.com/protocol/socks4a.protocol