Ok. It now reads:
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.
Also be warned that this will expose your users
proxy
password to the peer. USE WITH CAUTION
No, there is no performance concerns, only security concerns. If you
enable this to peers not in your administrative domain then you will
forward your users passwords to these peers, which is generally not a
wise thing to do..
Regards
Henrik
Klavs Klavsen wrote:
>
> well.. something like this would have helped me understand it.. but that's
> just me.. I can't speak for the majority.
>
> use 'login=PASS' if users must authenticate against
> the upstream proxy.this will pass-on login credentials
> to cache_peer.
> 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
> Note: (is there any performance concerns in enabling
> this -
> if for instance you also had your main-site on the
> same peer).
>
Received on Fri Nov 23 2001 - 18:19:32 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:04:29 MST