Failed to access to a spacific site via squid-3.1.10-9.el6_3.x86_64
Issue
- A client application fails to access to a spacific web server via quid-3.1.10-9.el6_3.x86_64.
- The phenomenon doesn't happen with squid-2.6.
- The client application and quid-3.1 support HTTP/1.1. but the web site doesn't.
squid 3.1
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:38:24 +0900] "POST http://update-server/ HTTP/0.0" 417 4428 NONE:NONE
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:38:37 +0900] "POST http://update-server/ HTTP/0.0" 417 4428 NONE:NONE
squid 2.6
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:39:42 +0900] "POST http://update-server/ HTTP/1.1" 200 1056 TCP_MISS:DIRECT
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:39:42 +0900] "CONNECT update-server:443 HTTP/1.1" 200 5867 TCP_MISS:DIRECT
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:39:42 +0900] "CONNECT update-server:443 HTTP/1.1" 200 5069 TCP_MISS:DIRECT
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:39:42 +0900] "CONNECT update-server:443 HTTP/1.1" 200 5099 TCP_MISS:DIRECT
XXX.XXX.XXX.XXX - - [03/Oct/2012:10:39:43 +0900] "CONNECT update-server:443 HTTP/1.1" 200 8564
Environment
- Red Hat Enterprise Linux 6.3
- squid-3.1.10-9.el6_3.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.