Authentication to Squid is completely separate from authentication to 
WWW servers. The Squid configuration on authentication is unrelated 
to the WWW server configuration on authentication.
For a WWW site requiring authentication to be proxied the WWW server 
must support at least one authentication method that can be proxied. 
Normally this is "Basic HTTP authentication", also known as "Plain 
text authentication", but "Digest HTTP authentication" is also an 
option if supported by the server and expected clients
Note: not all servers or browsers supports Digest HTTP authentication 
yet.. has only been standardised since June 1999 with a earlier 
specification published in January 1997, but the support is starting 
to get widespread coverage now.
Regards
Henrik
On Wednesday 27 November 2002 14.47, Wong, Sherman wrote:
> Hi Gerard,
>
> You know, you really have shed some hope on this.
> I have the basic auth configured right and working.
> But after the user authenticate themself to the squid,
> they got an error message if they visit that server.
>
> I don't why, normally I do not need https to go
> to that server but it worked. It worked - means if I
> use https to get to the same page, it correctly prompted
> the me for the password and let me pass. Unfortunately,
> a lot of other feature would not work and the page is not
> displayed correctly.
>
> I was hoping there is something we can do on the squid
> configuration to get this fixed. As I wrote email to them asking
> them to change the authentication method, they don't know what I am
> refering to. (Me neither.)
>
> Regards,
> Sherman
Received on Wed Nov 27 2002 - 07:38:22 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:11:36 MST