From: Chuck Murcko <chuck@apache.org>
Date: Thu, 20 Feb 1997 04:26:07 +0000 (+0000)
Subject: Fix typo; add section about SOCKS 4.2/Solaris problems.
X-Git-Tag: APACHE_1_2b7~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8e8309b1de6929d0e1b66d3037635bbfeac88244;p=thirdparty%2Fapache%2Fhttpd.git

Fix typo; add section about SOCKS 4.2/Solaris problems.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77650 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_proxy.html b/docs/manual/mod/mod_proxy.html
index 36d44aeaabf..5d0807b75dc 100644
--- a/docs/manual/mod/mod_proxy.html
+++ b/docs/manual/mod/mod_proxy.html
@@ -312,10 +312,13 @@ depending on the speed with which the hostname lookups occur.<p>
 Yes. Just build Apache with the rule <code>SOCKS4=yes</code> in your
 <i>Configuration</i> file, and follow the instructions there. SOCKS5 
 capability can be added in a similar way (there's no <code>SOCKS5</code>
-rule yet, so use the <code>EXTRA_LFLAGS</code> definition, or build Apache
+rule yet), so use the <code>EXTRA_LFLAGS</code> definition, or build Apache
 normally and run it with the <i>runsocks</i> wrapper provided with SOCKS5,
 if your OS supports dynamically linked libraries.<p>
 
+Some users have reported problems when using SOCKS version 4.2 on Solaris.
+The problem was solved by upgrading to SOCKS 4.3.<p>
+
 Remember that you'll also have to grant access to your Apache proxy machine by
 permitting connections on the appropriate ports in your SOCKS daemon's
 configuration.<p>