The software forwarded a malformed 302 response that should have been rejected as a parse error. This occurred because the `Transfer-Encoding: chunked` carve-out bypassed the rejection path. Consequently, a response that two peers can interpret differently is stored and served, leading to cache poisoning and response-framing desync.