+++ This bug was initially created as a clone of Bug #607870 +++ Description of problem: When using wget with a --header="Range: bytes=[number]-" header, wget doesn't recognize the 206 partial content response as valid and keeps retrying with: HTTP request sent, awaiting response... 206 Partial Content Retrying. Version-Release number of selected component (if applicable): GNU Wget 1.11.4 Red Hat modified How reproducible: Always. Steps to Reproduce: 1. wget --header="Range: bytes=1-" http://www.redhat.com 2. 3. Actual results: --2010-06-24 22:44:27-- http://www.redhat.com/ Resolving www.redhat.com... 184.50.224.112 Connecting to www.redhat.com|184.50.224.112|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Retrying. --2010-06-24 22:44:28-- (try: 2) http://www.redhat.com/ Connecting to www.redhat.com|184.50.224.112|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Retrying. --2010-06-24 22:44:30-- (try: 3) http://www.redhat.com/ Connecting to www.redhat.com|184.50.224.112|:80... connected. HTTP request sent, awaiting response... 206 Partial Content Retrying. Expected results: --2010-06-24 22:44:02-- http://www.redhat.com/ Resolving www.redhat.com... 184.50.224.112 Connecting to www.redhat.com|184.50.224.112|:80... connected. HTTP request sent, awaiting response... 206 OK Length: 19546 (19K) [text/html] Saving to: `index.html' 100%[===================================================================================================================================================================================================>] 19,546 --.-K/s in 0.04s 2010-06-24 22:44:02 (537 KB/s) - `index.html' saved [19545/19546] Additional info: Seems to have broken after wget 1.9 and fixed with a feature addition http://savannah.gnu.org/bugs/?func=detailitem&item_id=20416
This is a RHEL6 Bug clone to keep track of this "issue". There needs to be a wider discussion in the upstream about how this should be fixed.
Since upstream is aware of this issue and because of uncertainty how to properly solve issues arising with this feature it is highly unlikely it will be implemented by Fedora maintainer. Closing as UPSTREAM since there is no reason to keep this opened in Fedora.