Please excuse if this bug has already been reported:
In wget 1.8.1 (OS X) and 1.8.2 (cygwin) the handling of resources with
content-length 0 is wrong. wget tries to read the empty content and
hangs until the socket read timeout fires. (I set the timeout to
different
values and it exactly matches
Stefan Eissing [EMAIL PROTECTED] writes:
Of course this is only noticable with HTTP/1.1 server which leave
the connection open and do not apply transfer-encding: chunked for
empty response bodies.
They may not apply chunked transfer because Wget doesn't know how to
handle it. And leaving the
Stefan Eissing [EMAIL PROTECTED] writes:
Please excuse if this bug has already been reported:
In wget 1.8.1 (OS X) and 1.8.2 (cygwin) the handling of resources
with content-length 0 is wrong. wget tries to read the empty content
and hangs until the socket read timeout fires. (I set the
