[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Body skipped for non-GET

From: Ángel González
Subject: Re: [Bug-wget] Body skipped for non-GET
Date: Wed, 26 Jun 2013 01:48:59 +0200
User-agent: Thunderbird

Om 25/06/13 23:10, Darshit Shah wrote:

    Not does it only act differently, but on master it will start
    looping for --tries due to "Connection closed at byte 0.
    Retrying." which is no more than wget itself skipping the full
    body, then retrying because there's no body left.

You are correct. Since I was under the (wrong) idea that a page should not return a message body to a POST request, I did not include that case in my manual tests. I have however corrected this issue. This also prevent a behaviour change against 1.14. Hopefully, everything works smoothly now.
Yes. Looks good.

    Hmm. Right. It does what you intended, even if I considered that a
    bug. We need to decide which is the right thing to do, then.

I am not sure of the specs, but if servers do respond with a message body, Wget MUST read it and download it. Hence, I have removed the offending line of code and will now allow Wget to download the response body.
Fine :)

I also noted that with --method=head, --spider is automatically enabled (main.c:1405), which
produces some funny messages:

If there is a good reply:
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.

Remote file does not exist -- broken link!!!

sometimes with:
Spider mode enabled. Check if remote file exists.

which are a bit unexpected when the user didn't request --spider :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]