From f14ceed06b47c2f2275f70f2834aab25b160aff6 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Tue, 21 Dec 2004 05:43:17 +0000 Subject: capitalize acronyms, clarify windows doc a bit. svn:r3197 --- socks-extensions.txt | 2 +- tor-spec.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/socks-extensions.txt b/socks-extensions.txt index b2988ef..2cb6f7f 100644 --- a/socks-extensions.txt +++ b/socks-extensions.txt @@ -48,7 +48,7 @@ Tor's extensions to the SOCKS protocol 3. HTTP-resistance - Tor checks the first byte of each socks request to see whether it looks + Tor checks the first byte of each SOCKS request to see whether it looks more like an HTTP request (that is, it starts with a "G", "H", or "P"). If so, Tor returns a small webpage, telling the user that his/her browser is misconfigured. This is helpful for the many users who mistakenly try to diff --git a/tor-spec.txt b/tor-spec.txt index 073c685..58aa296 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -838,7 +838,7 @@ entries. 7.4. Behavior of a directory server lists nodes that are connected currently -speaks http on a socket, spits out directory on request +speaks HTTP on a socket, spits out directory on request Directory servers listen on a certain port (the DirPort), and speak a limited version of HTTP 1.0. Clients send either GET or POST commands. @@ -852,7 +852,7 @@ The basic interactions are: request containing the descriptor. "host" is used to specify the address:port of the dirserver, so - the request can survive going through http proxies. + the request can survive going through HTTP proxies. A.1. Differences between spec and implementation -- cgit v1.2.3-54-g00ecf