Re: [SQU] IBM Host On Demand

Ah, gotcha... but why would anyone use transparent proxying? If there is
ever the off chance the user needs to go to a website to authenticate, they
are technically "broken".

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Colin Campbell" <sgcccdc@citec.qld.gov.au>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: <squid-users@ircache.net>
Sent: Wednesday, February 14, 2001 4:41 PM
Subject: Re: [SQU] IBM Host On Demand

> Hi,
>
> On Wed, 14 Feb 2001, Adam Lang wrote:
>
> > Finally, can you explain to me why transparent proxies break the HTTP
> > authentication?
>
> They don't break HTTP authentication. They break proxy authentication.
> There are two authentication fields available in the HTTP header sent from
> the browser. One is for the destination web server, the other for proxy
> authentication. If the browser does not believe there is a proxy present,
> as is the case with transparent proxies, it will not react to a request
> for proxy auth and not send a proxy-auth field in the header.
>
> Colin

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html