bugGNU Wget - Bugs: bug #33253, wget and 206 with Content-Length: 0

 
 

bug #33253: wget and 206 with Content-Length: 0

Submitted by:  None
Submitted on:  Sat 07 May 2011 04:22:24 AM UTC  
 
Category: Program LogicSeverity: 3 - Normal
Priority: 5 - NormalStatus: None
Privacy: PublicAssigned to: None
Originator Name: Dirk ReinersOriginator Email: -unavailable-
Open/Closed: OpenRelease: 1.12
Operating System: GNU/LinuxReproducibility: Every Time
Fixed Release: NonePlanned Release: None
Regression: NoneWork Required: None
Patch Included: No

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sat 07 May 2011 04:22:24 AM UTC, original submission:

I'm using wget to retrieve large files over an unreliable connection, and it fails a lot. So I use wget -c to retry and continue downloading the files.

Unfortunately when the file is already finished and I retry the server sends a "206 Partial content" response with "Content-Length: 0", which wget interprets as failure and retries, and finally fails with return code 4 (network failure).

This seems to be specific for older versions of nginx (0.7.67 is where I found it), newer versions respond with a "416 Requested Range Not Satisfiable", which wget interprets correctly.

So it sounds like it's a server bug more than a wget bug, but it would be nice if it handled this situation more gracefully.

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by None (Submitted the item)
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup1