https://issues.apache.org/bugzilla/show_bug.cgi?id=50317
--- Comment #1 from Rein Tollevik <[email protected]> 2011-09-28 11:50:51 UTC --- The problem reported here appear to be fixed in cache_storage.c revision 1023398, which is in trunk and 2.3. It should imo be backported to 2.2, as thundering herd protection now effectively requires either Last-Modified or ETag headers in the cached response. Headers which are seldom present in dynamically generated content, which happen to be exactly the type of content I find it useful to cache :-( I found this report while investigating why the thundering herd protection didn't work as expected. The comment about the cache lock in the bug report appear to be bogus. The second call to ap_cache_try_lock is for the case when there are no cached content. The lock is only acquired by ap_cache_check_freshness when it finds stale content in the cache. ap_cache_try_lock will generate the cache key based on the requested URL when its third argument is NULL, and it will notice that the lock is already held if called for a second time for the same request. -- Rein Tollevik Basefarm AS -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
