Re: Incorrect HTTP range request with CURLOPT_RESUME_FROM_LARGE
Date: Mon, 30 Jun 2008 12:50:42 +0200 (CEST)
On Mon, 30 Jun 2008, Stephen Collyer wrote:
>> ./hx -5248835289980310801
> Well spotted, once again. Yes, that's probably what's happening. It hadn't
> occurred to me that the leading "-" was part of the number. However, that
> implies a minor bug in curl, I think. The range request value should be
> interpreted as an unsigned long long, since it never makes sense to send a
> negative range.
True, but this should only be a real problem if you try to get range >2GB with
libcurl built to not use large files, or in your case (libcurls built with
large file support) ranges above 9223372036854775808 bytes... :-)
Still a nice catch. I'll commit a fix for this in a minute.
-- / daniel.haxx.seReceived on 2008-06-30