Re: [PATCH] send HTTP/1.1 requests to HTTP servers for selected requests

On Sun, 21 Feb 2010 22:16:10 +0100, Henrik Nordström
<henrik_at_henriknordstrom.net> 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?
>
> To my understanding our HTTP client is fairly complete wrt HTTP/1.1
> requirements.
>
> 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.
>

Just the case you keep kicking me about whenever I propose this:
  That we also have to cater for broken clients when sending 417 back for
"Expect: 100-continue" requests.

Ignoring those clients and acting strictly 1.1 compliant we are ready
TODAY to enable 1.1 on the server side of Squid-3.1.

I have a HTTP/1.1 branch in launchpad partially complete which enables it
in strict mode (--disable-http-violations). NP: without any special config
options hacking around things.

I'll start pushing 1.1 compliance again when the auth blocker bugs are
closed and tested.

Amos
Received on Mon Feb 22 2010 - 02:20:48 MST