DO NOT REPLY [Bug 14556] - mod_cache with mod_mem_cache enabled doesnt cash modified documents

[bu...@apache.org]

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

rederpj@remulak.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From rederpj@remulak.net  2002-11-21 22:07 -------
Thanks for the diagnosis and input. I have committed a fix for this PR which
will be shipped in a future release of Apache.

The fix simply changes the checking code in mod_cache (around line 853) from

if (lastmod != APR_DATE_BAD)

to

if ((lastmod != APR_DATE_BAD) && (lastmod < date))

This forces the code into the else clause when lastmod == date.

You should not remove the "if lastmod>date then lastmod=date" code
since this has other negative consequences in checking for freshness.
Also, adding the conf->defex value into the expiry date calculation, as you
did, will either result in a longer than expected expiry date, or an expiry
date of maxexpire.

Please let me know if the above fix (adding "&& (lastmod < date))") fails to
solve the problem for you.

Thanks for using Apache and helping to make it better.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org