Subject: | Buggy EOF handling behaviour around connection caching/reuse |
If the (cached) connection happens to be at EOF condition but the
response reader hasn't read this far yet, the next use of that connection
fails with
Connection closed while awaiting header
Unclear quite how to handle this case, and also the related problems of
SIGPIPE from writing to it.
Needs more unit tests and fixing.
--
Paul Evans