DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14556>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14556 mod_cache with mod_mem_cache enabled doesnt cash modified documents [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Version|2.0.43 |2.0.44 ------- Additional Comments From [EMAIL PROTECTED] 2003-01-25 16:29 ------- The problem still in 2.0.44. With the fix above modified documents will never use this formula: expiry date = now + min((date - lastmod) * factor, maxexpire), because the "Date" header doesnt refresh never, lastmod always will be greater than date, isnt that a bug? So, the string around line 704 (in 2.0.44 mod_cache.c) should be changed from if (info->date == APR_DATE_BAD){ /* No, or bad date */ to if ((info->date == APR_DATE_BAD) || (lastmod > date)){ /* No, or bad date */ that will make "Date" header updated with *now* if document was modified and lastmod wont be greater than date. So the formula with conf->factor will work. Also that string around line 752 that is now if ((lastmod != APR_DATE_BAD) && (lastmod < date)) { should be changed to if ((lastmod != APR_DATE_BAD) && (lastmod <= date)) { Because in some cases, then the document was modified in the same time(same second) as requested by server, it should really expired by now and not be cached for default time. With these fixes above, it will be possible to configure the server to cache the documents for some time, BUT the documents that is modified for example every 1 second, automatically will be almost not cached. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
