Ruediger Pluem wrote:
Thanks to Jim for reviewing the patch. He detected one missed patch and made some comments in the code clearer. The new patch list now:
Quick consideration; Rather than look for HTTP_BAD_GATEWAY error bucket, we can actually generalize the problem. ANY metadata bucket that isn't recognized and handled by an intermediate filter probably indiciates a problem; and therefore the result is a non-cacheable, broken response. Thoughts? Bill
