Oliver Kindernay wrote:
Hi, I have webservers on virtual interfaces and SQUID3 in accelerator on interface with public IP on port 80. I am using "cache_peer" to forward request to webservers from internet. This is what I have in configuration file cache_peer 192.168.0.1 parent 80 0 no-query originserver no-digest name=server1 cache_peer 192.168.0.2 parent 80 0 no-query originserver no-digest name=server2 acl srvone dstdomain binpot.eu http_access allow srvone cache_peer_access server1 allow srvone cache_peer_access server1 deny all acl srvtwo dstdomain parky.binpot.eu http_access allow srvtwo cache_peer_access server2 allow srvtwo cache_peer_access server2 deny all It works, but it uses HTTP 1.0 for contact webservers. I want to use HTTP 1.1. How to achieve this? Or better, how to just forward _unchanged request_ from internet to webserver and than _unchanged request_ from webserver to client? I know squid 2.6 has some experimental HTTP 1.1 support for this, but I want to use squid3.
Squid is an RFC compliant HTTP proxy. It does _always_ alters the headers in compliance with HTTP standards.
Most of the features of HTTP/1.1 will work through Squid now despite the 1.0 being stated.
Squid 2.6 had experimental support for many HTTP/1.1 features which are now built in and working by default. Squid-2.7 had experimental support to advertise 1.1 despite some broken features. This has proven to be a mistake for many people.
The latest Squid-3.x betas are the most 1.1-enabled releases ever and we will make Squid-3 send 1.1 when it's actually compliant.
So patience please, or better yet some sponsorship to help speed the work up.
http://wiki.squid-cache.org/Features/HTTP11 Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20 Current Beta Squid 3.1.0.15
