BobSammers wrote: > I > I note the word "expires" close to a date a month from now. This might > explain (if this is being processed and overriding the 1 hour default > that was mentioned) why the entries are not being removed. The number > before the phrase "content-length" is probably pretty accurate for the > size of the non-text part of the cached value. > > I don't know where this is from; perhaps someone else can tell, but can > it really be the result of multiple URL requests you have identified, as > it's ~250K of binary data? Perhaps these entries (over 200 of them) were > in my cache for some other reason.
I am use LMS cache so it behaviour is the same for all user of the cache. AFAICT when an entry expires it is not removed - just not used. Purging clears out the cache but it doesn't occur for first time maybe 8h. I did a test and reduced the time for a purge and afterwards - cache size was still big but I didn't check contents. The http header expires relates to the validity of of the page so for a BBC program on iPlayer it will be about 28 days - I think the "expires" is not used by Cache in the plugin just the URL matching and "expires" is only important if it is less than the cache's own expiry time. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=104672 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
