From: hno <>
Date: Sat, 24 Nov 2001 06:38:52 +0000 (+0000)
Subject: Better explanations for login=PASS option
X-Git-Tag: SQUID_3_0_PRE1~1276
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ac3e132380f9870d89630b0933812074410bacc9;p=thirdparty%2Fsquid.git

Better explanations for login=PASS option
---

diff --git a/src/cf.data.pre b/src/cf.data.pre
index b1318bf84b..4304cd9fcb 100644
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -1,6 +1,6 @@
 
 #
-# $Id: cf.data.pre,v 1.240 2001/11/20 12:26:58 hno Exp $
+# $Id: cf.data.pre,v 1.241 2001/11/23 23:38:52 hno Exp $
 #
 #
 # SQUID Web Proxy Cache          http://www.squid-cache.org/
@@ -329,11 +329,13 @@ DOC_START
 		     spaces). This also means that % must be written as %%.
 
 		     use 'login=PASS' if users must authenticate against
-		     the upstream proxy. Note: To combine this with
-		     proxy_auth both proxies must share the same user
+		     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.
 		     Also be warned that this will expose your users proxy
-		     password to the parent. USE WITH CAUTION
+		     password to the peer. USE WITH CAUTION
 
 		     use 'login=*:password' to pass the username to the
 		     upstream cache, but with a fixed password. This is meant