Colin Campbell wrote:
> No authentication method can work with a transparent proxy. How can the
> browser send a "proxy-authentication" field in the HTTP headers when, as
> far as it knows, there's no proxy in use? Think about it. It's not squid
> that would need fixing. You'd need to fix the browser so that when it got
> a "407(?) proxy authentication required" it would request a password and
> forward that to the non-existant proxy in the HTTP headers of the request.
Won't happen as doing so introduces a BIG security hole in HTTP as the
browser has no means of knowing for sure there is a proxy... (it might
be the remote origin server requesting proxy authentication, hoping that
some stupid users enter their logon password information..)
A correct "fix" is to "fix" the browser to have a proxy configured. This
can be done by manual or automatic means (see for example WPAD,
available in all current Microsoft browsers... and some Mozilla versions
I think).
-- Henrik Nordstrom Squid HackerReceived on Tue Jun 05 2001 - 18:16:27 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:00:30 MST