Re: mod_cache deliver 304 instead of (not so) stale cache entries

[EMAIL PROTECTED] wrote: Sander Striker wrote: [EMAIL PROTECTED] wrote: [...] Might as well not do revalidation in that case; actually that would be better, because the 304's that are returned may not even be correct. The conditions are replaced with the ones from the cache, remember? Yes

Re: mod_cache deliver 304 instead of (not so) stale cache entries

Sander Striker wrote: >> [EMAIL PROTECTED] wrote: > > [...] [...] > >> I am aware that this forces a full request to the backend for requests >> without conditionals >> to expired resources. So I am not very happy with this solution. Maybe >> it is better to let >> the default handler pass 30

Re: mod_cache deliver 304 instead of (not so) stale cache entries

[EMAIL PROTECTED] wrote: [...] I found out that during the second request which returns a 304 the CACHE_SAVE filter, which would be able to deal with such things (-> (not so) stale cache entries) is never used. The change of the conditionals in cache_storage.c starting at line 269 leads to th

mod_cache deliver 304 instead of (not so) stale cache entries

Hi all, I think I found a problem with mod_cache of the httpd trunk (revision 171201). First off all I added the following configuration directives to the default httpd.conf: CacheRoot /home/ruediger/apache_head/apache_trunk/cache CacheEnable disk /test CacheMaxFilesize 1 CacheDirLevels