Bug #1238: Explain the login= cache_peer option more clearly

[thirdparty/squid.git] / src / cf.data.pre

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 8c27869862e36bc97ce2a4d9b8316d5399bfc554..9f994933b898acbc96df20adc222cdd4271fd0f1 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -1,6 +1,6 @@
 
 #
-# $Id: cf.data.pre,v 1.374 2005/02/09 13:01:40 serassio Exp $
+# $Id: cf.data.pre,v 1.375 2005/02/19 16:03:33 hno Exp $
 #
 #
 # SQUID Web Proxy Cache          http://www.squid-cache.org/
@@ -543,11 +543,13 @@ DOC_START
                     spaces). This also means % must be written as %%.
 
                     use 'login=PASS' if users must authenticate against
-                    the upstream proxy. This will pass the users credentials
-                    as they are to the peer proxy. This only works for the
-                    Basic HTTP authentication sheme. Note: To combine this
-                    with proxy_auth both proxies must share the same user
-                    database as HTTP only allows for one proxy login.
+                    the upstream proxy or in the case of a reverse proxy
+                    configuration, the origin web server.  This will pass
+                    the users credentials as they are to the peer.
+                    This only works for the Basic HTTP authentication scheme.
+                    Note: To combine this with proxy_auth both proxies must
+                    share the same user database as HTTP only allows for
+                    one proxy login.
                     Also be warned this will expose your users proxy
                     password to the peer. USE WITH CAUTION