Henrik Nordström wrote:
sön 2010-02-21 klockan 20:37 +0200 skrev Tsantilas Christos:
There are broken servers out there that insist on receiving HTTP/1.1
requests.
Yes..
and even more which are broken when receiving HTTP/1.0 requests.
This patch adds a new force_http_1p1_request acl-driven option to
squid.conf.
Question: What is missing for enabling HTTP/1.1 as the default outgoing
protocol version when forwarding requests?
Good question.
To my understanding our HTTP client is fairly complete wrt HTTP/1.1
requirements.
We are supporting chunked encodings, and HTTP 1.1 persistent connections.
Looks that most of the HTTP 1.1 new features are not used if the HTTP
client does not ask them.
Looks that you have right but I did not check very carefully the rfcs.
Maybe the force_http_1p1_request should implemented as
force_http_1p0_request :-)
Sure there is still some major missing pieces to reliably announce
ourselves as HTTP/1.1 to clients, but should not be much missing when
forwarding requests..
Regards
Henrik
