Hmm, that's a good idea.

By the way, here are some smaller links which also exhibit the problem, but
which won't take forever to download:

http://www.ngdc.noaa.gov/mgg/global/relief/ETOPO1/image/readme_color_etopo1_image.txt
[2.2KB]
http://www.ngdc.noaa.gov/mgg/global/relief/ETOPO1/docs/ETOPO1.pdf [3.1MB]
http://www.ngdc.noaa.gov/mgg/global/relief/ETOPO1/image/etopo1_southpole_hillshade.tif.zip
[34MB]

Robert

On Fri, Aug 22, 2014 at 2:24 PM, m brandenberg <mcbinc_at_panix.com> wrote:

> On Fri, 22 Aug 2014, Robert Xiao wrote:
>
> cURL may erroneously produce this error:
>>
>> curl: (33) HTTP server doesn't seem to support byte ranges. Cannot
>>> resume.
>>>
>>
>> when asked to continue downloading a file that is already completed. This
>> happens with servers that do not send Content-Range headers when replying
>> with the HTTP 416 error ("Requested Range Not Satisfiable"), even if the
>> server ordinarily supports Content-Range. In particular, when attempting
>> to
>> continue a completed download, cURL will request a byte range past the end
>> of the file, which triggers a 416 error.
>>
>
> Not a comment on the issue but a further observation: Some caches,
> e.g. Varnish, will send a 200 and the entire object in response to
> a completely unsatisfyable Range: request rather than a 416. Resuming
> with a one-byte overlap with the existing content can help avoid this
> unnecessary download.
>
> --
> Monty Brandenberg, Software Engineer MCB,
> Inc.
> mcbinc_at_panix.com P.O. Box
> 425292
> mcbinc_at_pobox.com Cambridge, MA
> 02142-0006
> 617.864.6907
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-08-22