Fix the bug in HTTP/1.1 reponse with Content-Length:0

In a multithread case one HTTP session is used for sending/receiving
HTTP requests/responses in parallel. This causes wrong parsing of responses if
Content-Length header is "0".

The bug is reported to the erlang bug list:
http://erlang.org/pipermail/erlang-bugs/2013-February/003391.html