Re: squid uses HTTP/1.0 ?

Squid _does_ use HTTP/1.0, or at least announces that it does. I _think_
that's correct per spec, since (although it uses many features from
HTTP/1.1) it does not use the right set of HTTP/1.1 features to announce
that protocol to it's peers (by 'peers' in this sentence, I am referring
to any server that the proxy communicates with, not just siblings and
parents).

What I _do_ find odd behaviour is that the web-server is not giving out
Cache-control headers on a 1.0 request. There's no reason for it _not_
to....HTTP implementations are supposed to ignore header lines that they
do not understand...therefore, aside from a microscopic bit of extra
bandwidth, one should be generous and send the header...many
applications that do not support full HTTP/1.1 compliance support things
like Cache-control.

After all, many of the features that we take as read as being a part of
the 1.0 spec aren't in there. They didn't become official until 1.1.

I'd really class this as 'unusual' behaviour on the part of the
web-server.

D

Charles Bruneteau wrote:
>
> hi,
>
> some pages on a Netscape Enterprise 3.0 are configured to be cached 1 day :
>
> # telnet webserver 80
> ...
> HEAD /cadences/file.xls HTTP/1.1
> host: webserver
>
> HTTP/1.1 200 OK
> Server: Netscape-Enterprise/3.0K
> Date: Fri, 10 Sep 1999 08:33:32 GMT
> Cache-control: "max-age=86400"
> Content-type: application/x-excel
> Etag: "76b90-4600-37d75390"
> Last-modified: Thu, 09 Sep 1999 06:28:32 GMT
> Content-length: 17920
> Accept-ranges: bytes
>
> However our squid proxies (2.2s4) keep answering with object from their cache which are older than 1 day :
>
> # telnet squidproxy 3333
> HEAD http://webserver/cadences/file.xls HTTP/1.1
>
> HTTP/1.0 200 OK
> Server: Netscape-Enterprise/3.0K
> Date: Thu, 09 Sep 1999 05:35:09 GMT
> Content-Type: application/x-excel
> Last-Modified: Thu, 11 Mar 1999 08:05:42 GMT
> Content-Length: 69632
> Accept-Ranges: bytes
> Age: 92880
> X-Cache: HIT from squidproxy
> Proxy-Connection: keep-alive
>
> 92880 > 86400, isn't it ?
>
> i was surprised to see HTTP/1.0 in the last header. Therefore i tried several requests, and it seems that, even if squid receive a HTTP/1.1 request, it uses HTTP/1.0 with the Netscape server (which uses HTTP/1.1) !!!
>
> And when the Netscape server gets a HTTP/1.0 request, it doesn't respond with the "Cache-control" directive; this sounds natural.
>
> So what's wrong with this ? Does squid only use HTTP/1.0 ? Do i have a bad negociation between squid and Netscape ?
>
> Thanks
>
> Charles Bruneteau
Received on Fri Sep 10 1999 - 04:31:44 MDT