On Mon, May 23, 2016 at 6:24 AM, Rob Landrito wrote:
> The specific circumstance is described in a comment in mod_cache:
>
> /* Hold the phone. Some servers might allow us to cache a 2xx, but
> * then make their 304 responses non cacheable. This leaves us in a
>
Under a very specific set of circumstances, apache proxy will not serve
the correct headers for cached content. This was observed under 2.2.29
and seems to exist in the 2.2.31 release.
The problem occurs when a client revalidates content that is both
already cached on the client, and on the