git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] http.c: use CURLOPT_RANGE for range requests

From
Jeff King <peff@peff.net>
Date
Nov 2, 2015, 01:51 UTC
Message-ID
<20151102015157.GA25597@sigill.intra.peff.net>
In-Reply-To
<alpine.DEB.2.11.1511012359150.24283@tvnag.unkk.fr>
On Mon, Nov 02, 2015 at 12:00:42AM +0100, Daniel Stenberg wrote:
Show 9 quoted lines
> On Fri, 30 Oct 2015, Jeff King wrote:
> 
> >The goal makes sense. Why weren't we using CURLOPT_RANGE before? Did it
> >not exist (or otherwise have limitations) in 2005, and if so, when did it
> >become usable? Do we need to protect this with an #ifdef for the curl
> >version?
> 
> CURLOPT_RANGE existed already in the first libcurl release: version 7.1,
> relased in August 2000.
Ah, thanks. I guess we don't have to worry about that, then.

While I have your attention, Daniel, am I correct in assuming that performing a second unrelated request with the same CURL object will need an explicit:

  curl_easy_setopt(curl, CURLOPT_RANGE, NULL);
to avoid using the range twice?
-Peff
Previous: Daniel StenbergNext: Daniel Stenberg
Message 7 of 8 in “http.c: use CURLOPT_RANGE for range requests”
  1. http.c: use CURLOPT_RANGE for range requestsDavid Turner, Oct 30, 2015
  2. Junio C HamanoOct 30, 2015
  3. Jeff KingOct 31, 2015
  4. Junio C HamanoOct 31, 2015
  5. Jeff KingOct 31, 2015
  6. Daniel StenbergNov 1, 2015
  7. Jeff KingNov 2, 2015
  8. Daniel StenbergNov 2, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.