[Top][All Lists]

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

[Bug-wget] [bug #54963] wget -c treats a 416 response as a failure

From: Svein Ove Aas
Subject: [Bug-wget] [bug #54963] wget -c treats a 416 response as a failure
Date: Mon, 5 Nov 2018 10:39:52 -0500 (EST)
User-agent: Mozilla/5.0 (X11; CrOS x86_64 11021.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.76 Safari/537.36


                 Summary: wget -c treats a 416 response as a failure
                 Project: GNU Wget
            Submitted by: baughn
            Submitted on: Mon 05 Nov 2018 03:39:50 PM UTC
                Category: Protocol Issue
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 1.19.5
        Operating System: None
         Reproducibility: Every Time
           Fixed Release: None
         Planned Release: None
              Regression: Yes
           Work Required: None
          Patch Included: None



This was tested on NixOS 19.03pre-git (Koi), based on a report from a user on

With wget -c, the client issues a range request asking for any data that has
not yet been downloaded. For a file that has already been fully downloaded
this becomes an invalid request, asking for data that does not exist, and the
HTTP server should return a 416.

In wget 1.18, the 416 return is correctly treated as success.

For wget 1.19.5, this is treated as an error, and the download is retried. It
should be treated as success.

Example, for `wget -d -c -t 1 https://brage.info/robots.txt`:


Reply to this item at:


  Message sent via Savannah

reply via email to

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