Hi All,
I'm Akhaice.
# And now, thanks for developers and maintainers at all times.
I'm using squid-3.5.16.
Recently I upgraded from squid-3.1 to squid-3.5.
And I've been using ICAP Server that has authentication function.
I configured that users needed authentication when they access web site.
The authentication function were provided by ICAP Server.
When ICAP Server return response code 407 with "Proxy-Authenticate" header,
Client browser was not able to receive this header and display authentication dialog.
I captured packets in two places.
One is between squid and ICAP server. The other is between squid and Client browser.
The header information is as follows.
==================================================
+ From ICAP Server to Squid
ICAP/1.0 200 OK
Server: TEST-ICAP
ISTag: "TEST-ICAP"
Date: Thu, 04 Aug 2016 03:05:34 GMT
Cache-Control: no-cache
Connection: close
Encapsulated: res-hdr=0, res-body=232
HTTP/1.1 407 Proxy Authentication Required
Proxy-Connection: close
Content-Type: text/html; charset=utf-8
Proxy-Authenticate: Basic realm="TESTAUTH"
Pragma: no-cache
Expires: Tue, 2 2001 20:00:00 GMT
Content-Length: 2349
==================================================
+ From Squid to Client browser
HTTP/1.1 407 Proxy Authentication Required
Date: Thu, 04 Aug 2016 03:05:34 GMT
Content-Type: text/html; charset=utf-8
Pragma: no-cache
Expires: Tue, 2 2001 20:00:00 GMT
Content-Length: 2349
X-Cache: MISS from proxyserver.local
Connection: keep-alive
==================================================
I found that Squid-3.5 automatically deleted the Proxy-Authenticate header.
Is it the correct behavior on squid-3.5 ?
How can I make client browser get Proxy-Authenticate header?
Thank you.
John Akhaice
I'm Akhaice.
# And now, thanks for developers and maintainers at all times.
I'm using squid-3.5.16.
Recently I upgraded from squid-3.1 to squid-3.5.
And I've been using ICAP Server that has authentication function.
I configured that users needed authentication when they access web site.
The authentication function were provided by ICAP Server.
When ICAP Server return response code 407 with "Proxy-Authenticate" header,
Client browser was not able to receive this header and display authentication dialog.
I captured packets in two places.
One is between squid and ICAP server. The other is between squid and Client browser.
The header information is as follows.
==================================================
+ From ICAP Server to Squid
ICAP/1.0 200 OK
Server: TEST-ICAP
ISTag: "TEST-ICAP"
Date: Thu, 04 Aug 2016 03:05:34 GMT
Cache-Control: no-cache
Connection: close
Encapsulated: res-hdr=0, res-body=232
HTTP/1.1 407 Proxy Authentication Required
Proxy-Connection: close
Content-Type: text/html; charset=utf-8
Proxy-Authenticate: Basic realm="TESTAUTH"
Pragma: no-cache
Expires: Tue, 2 2001 20:00:00 GMT
Content-Length: 2349
==================================================
+ From Squid to Client browser
HTTP/1.1 407 Proxy Authentication Required
Date: Thu, 04 Aug 2016 03:05:34 GMT
Content-Type: text/html; charset=utf-8
Pragma: no-cache
Expires: Tue, 2 2001 20:00:00 GMT
Content-Length: 2349
X-Cache: MISS from proxyserver.local
Connection: keep-alive
==================================================
I found that Squid-3.5 automatically deleted the Proxy-Authenticate header.
Is it the correct behavior on squid-3.5 ?
How can I make client browser get Proxy-Authenticate header?
Thank you.
John Akhaice
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
