From 65fca573ee169505623b4b67fed527a261884fa9 Mon Sep 17 00:00:00 2001
From: hno <>
Date: Sat, 19 Feb 2005 23:03:33 +0000
Subject: [PATCH] Bug #1238: Explain the login= cache_peer option more clearly

---
 src/cf.data.pre | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 8c27869862..9f994933b8 100644
--- 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
 
-- 
2.39.5