RE: [squid-users] strange problem with www.evangel.org.sg

On Wed, 7 Sep 2005, Sturgis, Grant wrote:

> You browser is requesting http/1.0:
>
>> Trying 203.127.19.66...
>> Connected to evangel.org.sg (203.127.19.66).
>> Escape character is '^]'.
>> GET /index.html HTTP/1.0
>
> The server is responding in http/1.1:
>
>> HTTP/1.1 200 OK
>> Date: Wed, 07 Sep 2005 15:10:17 GMT
>> Server: Apache/2.0.49 (Unix) DAV/2 mod_fastcgi/2.4.2
>> mod_ssl/2.0.49 OpenSSL/0.9.6i
>
> This is not good. Most browsers and some proxies deal with this, squid does not.
>
> Henrik says that http/1.1 is in the works for the next version of squid.
>
> Regardless of squid's capabilities, a web server responding like this definitely means that the web server is broken.

Eh?

A HTTP/1.1 server should always answer with HTTP/1.1 even if the request
was HTTP/1.0. But there is several aspects of HTTP/1.1 the server MUST NOT
USE if the request was a HTTP/1.0 request. The main one is "Transfer
Encoding". For a complete list see RFC2616 HTTP/1.1.

It is correct that Squid is still HTTP/1.0. As a result requests (and
responses) forwarded via Squid is HTTP/1.0. But HTTP/1.1 clients and
servers should both advertise their HTTP/1.1 support in their messages to
Squid, even if Squid as such is using HTTP/1.0.

Regards
Henrik
Received on Sat Sep 10 2005 - 16:20:36 MDT