On Tue, 2006-02-21 at 10:03 -0600, Steve Brown wrote:
[...]
> In the specific scenario I mentioned, the browser isn't submitting any
> credentials. The traffic is being intercepted and routed through a
> local proxy which in turns forwards requests to a remote proxy w/
> authentication. It seems to me that the browser is completely unaware
> that there is any interception taking place. Isn't that the point?
[...]
> So what is the purpose of the login parameter for the peer_cache config
> option?
It seems that I misunderstood what you meant. Do you want the PROXY to
authenticate against its parent? Independently from who is the user it
acts in behalf of?
A confused Kinkie
