I've merged the above patches to master. They will be available with the next
version of Wget
* Darshit Shah [171208 18:47]:
> Hi,
>
> Thanks for your report. It is indeed a bug in Wget, as you've rightfully
> investigated. The socket still had some data which caused the next
If there's no objections by tomorrow, I'll push the patches to master after
adding Test-46.py to testenv/Makefile.am
* Darshit Shah [171208 18:47]:
> Hi,
>
> Thanks for your report. It is indeed a bug in Wget, as you've rightfully
> investigated. The socket still had some data
Hi,
Thanks for your report. It is indeed a bug in Wget, as you've rightfully
investigated. The socket still had some data which caused the next request to
have problems.
I've attached two patches here, the first one fixes the issue. It tries to read
and discard any HTTP body still available and
Hello wget developers,
I found an issue when using `wget -c`, as in:
https://github.com/mholt/caddy/issues/1965#issuecomment-349220927
By checking out the wget source code, I can confirm that it doesn't
drain the response body when it meets a 416 Requested Range Not
Satisfiable, and then the