> > > The other bug(?) I found was while using mod_cache together with a bogus > backend sending wrong timestamps in the headers leading to > > > [cache:info] [...] AH: cache: /myRequest?myQuery responded with an > uncacheable 304, retrying the request. Reason: contradiction: 304 Not > Modified, but Last-Modified modified, referer: https://my.host
It didn't make it into the changelog, but this is fixed in a later 2.4.x: - * mod_cache: Stop invalidating cached responses when reval returns 304+Expires, - trunk patch: http://svn.apache.org/r1518269 - 2.4.x patch: trunk works - +1 covener, jim, humbedooh
