Dieter Bloms wrote:
Hi,
we have a commercial software, which provides the credentials to the
squid proxy, when we run the 3.0.STABLE9, but doesn't, when we run
2.7.STABLE6.
When we run 2.7.STABLE6, the client does the requests without
credentials, even when squid answers with 407 HTTP code.
the only difference I see are different header entries in the
answer from squid like Mime-Version, Proxy-Connection and Via:
3.0.STABLE9:
HTTP/1.0 407 Proxy Authentication Required
Server: squid
Mime-Version: 1.0
Date: Wed, 25 Feb 2009 15:15:20 GMT
Content-Type: text/html
Content-Length: 2021
Expires: Wed, 25 Feb 2009 15:15:20 GMT
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Proxy-Authenticate: Basic realm="Proxy-Server"
X-Cache: MISS from FQDN
Via: 1.0 FQDN (squid)
Proxy-Connection: close
2.7.STABLE6:
HTTP/1.0 407 Proxy Authentication Required
Server: squid
Date: Wed, 25 Feb 2009 15:16:04 GMT
Content-Type: text/html
Content-Length: 2048
X-Squid-Error: ERR_CACHE_ACCESS_DENIED 0
Proxy-Authenticate: Basic realm="Proxy-Server"
X-Cache: MISS from FQDN
Via: 1.0 FQDN:8080 (squid)
Connection: close
so it is possible to configure 2.7.STABLE6 that it returns the same
heades like 3.0.STABLE9 does ?
Thank you very much.
Not without removing a lot of HTTP/1.1 support.
I think you should complain to the commercial vendors. They are making
bad assumptions about how HTTP works.
The only thing squid really has to send back is:
HTTP/1.0 407 Proxy Authentication Required
Date: Wed, 25 Feb 2009 15:15:20 GMT
Proxy-Authenticate: Basic realm="Proxy-Server"
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
Current Beta Squid 3.1.0.6
