Re: [squid-users] Diagnosing Objects That Are Not Cached (squid/3.0.STABLE8)

I enabled level 6 logging for section 22 and 65.  I then explicitly retrieved 'http://www.facebook.com/images/loaders/indicator_blue_small.gif' and found the following entries in cache.log. Does this confirm that the problem is the invalid 'Expires' header value? If so, is there a way around this issue other than trying to get Facebook to adhere to standards?
    Thanks, Norbert

2010/02/17 12:02:21.776| getMaxAge: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:02:22.298| ctx: enter level  0: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:02:22.298| refreshCheck: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:02:22.298| STALE: expires 1266426142 < check_time 1266426202
2010/02/17 12:02:22.298| Staleness = 60
2010/02/17 12:02:22.298| refreshCheck: Matched '. 0 20%% 259200'
2010/02/17 12:02:22.298| refreshCheck: age = 60
2010/02/17 12:02:22.298|        check_time:     Wed, 17 Feb 2010 17:03:22 GMT
2010/02/17 12:02:22.299|        entry->timestamp:       Wed, 17 Feb 2010 17:02:22 GMT
2010/02/17 12:02:22.299| refreshIsCachable() returned non-cacheable..
2010/02/17 12:02:29.656| ctx: exit level  0

2010/02/17 12:03:54.815| getMaxAge: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:03:55.106| ctx: enter level  0: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:03:55.106| refreshCheck: 'http://www.facebook.com/images/loaders/indicator_blue_small.gif'
2010/02/17 12:03:55.106| STALE: expires 1266426235 < check_time 1266426295
2010/02/17 12:03:55.106| Staleness = 60
2010/02/17 12:03:55.106| refreshCheck: Matched '. 0 20%% 259200'
2010/02/17 12:03:55.106| refreshCheck: age = 60
2010/02/17 12:03:55.106|        check_time:     Wed, 17 Feb 2010 17:04:55 GMT
2010/02/17 12:03:55.106|        entry->timestamp:       Wed, 17 Feb 2010 17:03:55 GMT
2010/02/17 12:03:55.107| refreshIsCachable() returned non-cacheable..
2010/02/17 12:04:07.020| ctx: exit level  0

> fre 2010-02-12 klockan 13:40 +1300 skrev Amos Jeffries:
> But even then Cache-Control max-age should have higher priority..
> Expires should only be looked at if there is no cc s-maxage/max-age.

> Regards
> Henrik

>> Chris Robertson wrote:

>> >> HTTP/1.1 200 OK
>> >> Accept-Ranges: bytes
>> >> Cache-Control: max-age=2592000
>> >> Content-Type: image/gif
>> >> Expires: Sat, 13 Mar 10 22:37:08 GMT
>> >> X-Cnection: close
>> >> Date: Thu, 11 Feb 2010 22:37:08 GMT
>> >> Content-Length: 522
>> >>
>> >> General: The Expires header's value isn't a valid date.
>>
>> That above is probably the killer. As we get closer to HTTP/1.1
>> compliance we get more things discarded for non-compliance.
>>
>> Invalid date maps to "-1" and non-cacheable.
Received on Wed Feb 17 2010 - 18:24:00 MST