Re: [squid-users] "auto-login" problems with newer web browsers

Your two mime captures simply show
(ie 6) a normal request followed by a 407 - proxy authentication
required
(ie 3) a normal request with proxy authentication followed by a 304 -
object not modified.

This is a client issue - IE and netscape have changed - there is no
change in Squid that I am aware of that will affect that behaviour.

Your best bet is to contact MS or Netscape and get a changelog between
the versions that work and don't work. (Good Luck!).

If squid can do something to assist, feel free to request it here. Some
of us developers will do custom modifications on a time and material
basis. Having said that, IMO there isn't anything (within the HTTP
RFC's) that Squid can do, as it's up to the browser to generate the
credentials (the client doesn't send the http://user:pw@url... to squid,
it turns it into at least two separate lines:
GET url HTTP/1.0
Proxy-Authorization: Basic <encoded user:pw>

Rob

===
----- Original Message -----
From: "Philip Bush" <phil@flipin.com>
To: <squid-users@squid-cache.org>
Sent: Thursday, January 10, 2002 2:28 AM
Subject: [squid-users] "auto-login" problems with newer web browsers

I'm having problems using "auto-login" (it was implemented into Squid in
2.1, I'm currently running 2.3 stable4). The proxy is set up to be a
traditional forward proxy.

I have had a very good look around to see what I can find on this
behaviour and I've got nothing at all solid as yet.

I've read RFC's 2068 (http 1.1), 2069 (Digest Authentication), 2616
(update to 2068) and 2617 and I haven't seen anything on authenticating
to a proxy server using the URL or if the username and password on the
URL to be only be allowed to be passed to the destination web server.

Has anyone got this type of authentication working on IE >= 5.01 or
Netscape >= 4.08?

Many thanks for your time to read this, any help / suggestions would be
greatly appreciated.

Philip Bush
Received on Wed Jan 09 2002 - 16:27:22 MST