The attached patch works around this problem by not calling ap_discard_request_body() on responses that never have a response body (1xx, 204, 205, 304).
Should ap_discard_request_body() not be intelligent enough itself to know whether a body is expected or not, and act accordingly? Perhaps a better fix is to teach ap_discard_request_body which responses never have one.
That routine is for HTTP requests, not response bodies. Why would it know anything about responses? There is a point at which reuse can be a bad thing.
....Roy
