Re: [squid-users] Squid 3.0 vs. 2.6 Releases

Amos Jeffries wrote:
>> On the authentication issue I tried changing log level to 9 for a
>> short time but it did not tell me much. Saw the POST when the
>> username and password was submitted but not much else. Its a IIS/6
>> server with ASP.NET version 2. Looks to be using javascript to log
>> in.
>>
>> Any ideas what I can change on Squid to make it work? Its does this
>> both in transparent and non-transparent modes. I was hoping maybe
>> Squid v3 had some improvements that would make it work.
>>
>
> Interception 'transparent' mode ports do not even attempt to perform
> authentication.

To clarify, interception/transparent proxy ports don't allow proxy
authentication. It should work just fine for authenticating to a web
server, be it via HTTP auth or a login form.

> Though with most javascript methods HTTP authentication is
> not involved anyway.
>

Given it's a form that's being POSTed, this doesn't sound like HTTP auth
in any case.

> Making sure the interception and direct-proxy listening ports are
> different should fix it for most users. If the code itself is failing on a
> side-band authentication there is nothing you can do to fix it in squid.
> Only the sites webmaster can fix those.
>

Unless Squid is configured to block some important header, or forced to
cache pages that are marked private, or...

A look at your squid.conf (without comments) might give the list members
a better opportunity to help.

> Amos
>

Chris
Received on Thu May 22 2008 - 15:29:06 MDT