Re: unexpected caching?

On Tue, 4 Aug 1998, Gerhard Brosig wrote:

> running squid 1.1.22 i wonder about some unexpected things.
> there are TCP_Miss for objects that should be in the cache.
> This is repeatable. Attached some infos from access.log and the requested objects.
>
> Try a document with expires header
> http://www.unitedmedia.com/comics/dilbert/
>
> Bits from the required document:
>
> <META HTTP-EQUIV="expires" CONTENT="Tue, 31 Dec 1996 01:23:45 GMT">
> <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
> <META HTTP-EQUIV="DESCRIPTION" content="The Dilbert Zone">
> <META name="KEYWORDS" content="comics, dilbert, dogbert, ratbert, catbert, comic books, cartoons, catbert, dnrc, Scott Adams">

There is no expires header in this document. The document content you cite is
irrelevant to Squid. HTTP _server_ may interpret those meta commands.
Apparently, the server is not- or mis-configured and does not interpret them.
Here is the _real_ http header:

HTTP/1.1 200 OK
Server: Netscape-Enterprise/3.5.1C
Date: Wed, 05 Aug 1998 16:57:20 GMT
Content-type: text/html
Link: <http://umweb2.unitedmedia.com/comics/dilbert/?PageServices>;rel="PageServices"
Last-modified: Wed, 05 Aug 1998 07:38:37 GMT
Content-length: 12676
Accept-ranges: bytes

 
> Try an url without expires-Header:
>
> http://www.cineca.it/proxy/search/

That page could be modified at the time. Their last modification date is Tue,
04 Aug 1998:

HTTP/1.1 200 OK
Date: Wed, 05 Aug 1998 17:04:08 GMT
Server: Apache/1.2b6
Connection: close
Content-Type: text/html
Last-Modified: Tue, 04 Aug 1998 09:37:40 GMT
ETag: "23046d-12e5-35c6d664"
Content-Length: 4837
Accept-Ranges: bytes

Alex.
Received on Wed Aug 05 1998 - 10:12:39 MDT