Re: [squid-users] why does squid not cache this page ?

http://www.mnot.net/cacheability/ reports:

       http://work.malmoe.at/artikel/funktionieren/26/index.html

            Expires -
        Cache-Control -
        Last-Modified -
             ETag -
       Content-Length - (actual size: 1196)
            Server ' - '

       This object will be considered stale, because it doesn't have any
freshness information assigned. It doesn't have a validator present. It
doesn't have a Content-Length header present, so it can't be used in a
HTTP/1.0 persistent connection.

Seems to be the case of most HTML content on that virtual host..

A manual request of http://work.malmoe.at reveals the following headers:

HTTP/1.1 200 OK^M
Date: Wed, 14 Nov 2001 08:58:28 GMT^M
expire: +10m^M
Connection: close^M
Content-Type: text/html; charset=UTF-8^M
^M

which could have been cached IF the expiration had correctly set.. now
it can't as there is no Expires header set, The header that is there is
named incorrectly, and the time is not formatted.

Regards
Henrik Nordström
Squid Hacker

Peter Pilsl wrote:
>
> I've a working squid, but now I run into a problem: squid does not
> cache the following page and I have no idea whats the problem is:
>
> http://work.malmoe.at/artikel/funktionieren/26/index.html
> or
> http://work.malmoe.at/artikel/funktionieren/26
>
> I repeatedely get the following entries in squid when requesting this
> page:
>
> 1005698249.856 727 127.0.0.1 TCP_MISS/200 1360 GET http://work.malmoe.at/artikel/funktionieren/26/index.html - DIRECT/work.malmoe.at text/html
> 1005698251.255 730 127.0.0.1 TCP_MISS/200 1360 GET http://work.malmoe.at/artikel/funktionieren/26/index.html - DIRECT/work.malmoe.at text/html
> 1005698252.349 724 127.0.0.1 TCP_MISS/200 1360 GET http://work.malmoe.at/artikel/funktionieren/26/index.html - DIRECT/work.malmoe.at text/html
> 1005698253.351 732 127.0.0.1 TCP_MISS/200 1360 GET http://work.malmoe.at/artikel/funktionieren/26/index.html - DIRECT/work.malmoe.at text/html
>
> or, reading the server/proxy-respond of a request:
> $ wget -Y on -S http://work.malmoe.at/artikel/tanzen/23/ind
> ex.html
> --01:38:38-- http://work.malmoe.at/artikel/tanzen/23/index.html
> => `index.html.18'
> Connecting to localhost:3128... connected!
> Proxy request sent, awaiting response... 200 OK
> 2 Date: Wed, 14 Nov 2001 00:38:44 GMT
> 3 expire: +1h
> 4 Content-Type: text/html; charset=UTF-8
> 5 X-Cache: MISS from localhost
> 6 Proxy-Connection: close
> 7
>
> other pages on the same server (same IP) are cached well, like
> http://www.malmoe.at
>
> 1005698680.035 1 127.0.0.1 TCP_HIT/200 1730 GET http://www.malmoe.at/ - NONE/- text/html
> 1005698681.063 1 127.0.0.1 TCP_HIT/200 1730 GET http://www.malmoe.at/ - NONE/- text/html
> 1005698681.678 1 127.0.0.1 TCP_HIT/200 1730 GET http://www.malmoe.at/ - NONE/- text/html
>
> Is this is a problem of my squid or is the page sending some
> information that is irritating my squid.
>
> I dont want to post my whole squid.conf here, but there is no entry
> that would especially affect this page.
>
> Can it have something to do with the fact, that the problematic page
> is the output of a script (which shouldnt even be noticed by squid,
> cause all html-headers like expire ... are set ...)
>
> thnx,
> peter
>
> --
> mag. peter pilsl
>
> phone: +43 676 3574035
> fax : +43 676 3546512
> email: pilsl@goldfisch.at
> sms : pilsl@max.mail.at
>
> pgp-key available
Received on Wed Nov 14 2001 - 02:05:16 MST