You need to reconfigure the web server to allow any of the standard
HTTP authentication shemes (Basic or Digest).
This big company calls "Basic HTTP Authentication" for "Plaintext
authentication". What they call Digest authentication I do not know,
but hopefully this is called Digest authentication..
Regards
Henrik
On Wednesday 27 November 2002 14.54, Wong, Sherman wrote:
> I know how you feel. That has grown to a size that may need quite
> some effort to fix. How do we fix it?
>
> Neither myself or the guy that owns the page knows how to fix it.
> Any suggestion??
>
> Regards,
> Sherman
>
> >===== Original Message From Henrik Nordstrom <hno@squid-cache.org>
> > ===== Because a certain very big company did not read the HTTP
> > specifications when implementing their "integrated login" schemes
> > (NTLM and then Negotiate), and as a result their design is in
> > violation to fundamental aspects of the HTTP specification and
> > cannot be proxied by standard HTTP proxies who try to follow the
> > specifications (not even their own proxy).
> >
> >Regards
> >Henrik
> >
> >"Wong, Sherman" wrote:
> >> I supposed authentication e.g. basic, is setup for authenticate
> >> users to
>
> use
>
> >> the cache. When the Web server needs authentication, it has
> >> nothing to do with the squid. Since the squid does not cache
> >> passwords. So it just
>
> forward
>
> >> the request. In that sense, why would the authentication method
> >> e.g. digest or ntlm possibly affecting the authentication
> >> process to the destination web server??
Received on Wed Nov 27 2002 - 07:06:52 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:11:36 MST