Peter Marshall wrote: > Anyway, ... all of my pages look the same ...(as far as I can tell ... but > I am far from being an expert) > > 1086272829.978 492 192.168.202.73 TCP_MISS/301 490 GET > http://members.rogers.com/worshipmusic - DIRECT/66.185.95.103 text/html > 1086272836.984 1033 192.168.202.73 TCP_MISS/301 490 GET > http://members.rogers.com/worshipmusic - DIRECT/66.185.95.103 text/html
>From http://www.web-caching.com/cacheability.html: "http://members.rogers.com/worshipmusic/ Clients have to follow 1 redirect(s) to get to this object. This may be uncacheable, and causes slowdowns. This object doesn't have any explicit freshness information set, so a cache may use Last-Modified to determine how fresh it is with an adaptive TTL (at this time, it could be, depending on the adaptive percent used, considered fresh for: 2 weeks 5 days (20%), 6 weeks 5 days (50%), 13 weeks 4 days (100%)). It can be validated with Last-Modified." Try www.squid-cache.org, which the test engine shows as cachable. Adam
