News for hackers. Stuff that matters.
Re:Curl vs. Wget by toupeira on Wednesday March 02, 2016 @06:41PM (#11213998)
-C requires you to specify the byte offset, and you also need --append or >> so it's not quite the same.
Re:Curl vs. Wget by hmpc on Wednesday March 02, 2016 @06:52PM (#11214056)
Actually no. From the manpage:

Use "-C -" to tell curl to automatically find out where/how to resume the transfer. It then uses the given output/input files to figure that out.

Re:Curl vs. Wget by foota on Thursday March 03, 2016 @03:43AM (#11215701)
Stupid question, but how do things like this resume from where they left off? Wouldn't the server need to be cooperating in this? Is that build into HTTP?
Re:Curl vs. Wget by laumars on Thursday March 03, 2016 @04:11AM (#11215778)
Yes the server would need to support it. The request is made via a HTTP header (Range[1] IIRC).

Also, I wouldn't consider that a stupid question. :)

[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#Rang...

Re:Curl vs. Wget by hobarrera on Thursday March 03, 2016 @08:42AM (#11216738)
This is also how download accelerators worked (back in the late nineties, early naught's), by having different connections work at several ranges to maximize bandwidth usage.
Re:Curl vs. Wget by laumars on Thursday March 03, 2016 @10:43AM (#11217497)
Funny enough, it was writing a download accelerator that taught me about the Range HTTP request header.
Re:Curl vs. Wget by zo1 on Thursday March 03, 2016 @04:07AM (#11215772)
You specify a byte "range" when requesting a file via HTTP from the server. Not all servers support this, but most do these days.

#Edit. More info here: https://en.wikipedia.org/wiki/Byte_serving

Re:Curl vs. Wget by viperscape on Thursday March 03, 2016 @06:13AM (#11216146)
Just looked that up, that's a rather limited usefulness. The multi homed usage makes sense but feels out of place really.
Re:Curl vs. Wget by joosters on Thursday March 03, 2016 @06:57AM (#11216289)
Why? How could it be more useful? HTTP byte ranges are incredibly flexible, since you one request can specify many byte ranges at once (it's almost too flexible, since a dumb server can easily be overwhelmed by a maliciously complicated request)

It handles the basic case of fetching the remainder of an interrupted download, and can also support partial downloads e.g. for supporting a video stream with the user jumping to different places in the movie.

Re:Curl vs. Wget by raverbashing on Thursday March 03, 2016 @12:14AM (#11215163)
Correct, but very unintuitive
Re:Curl vs. Wget by lmz on Thursday March 03, 2016 @12:54AM (#11215266)
Also doesn't work with the command line utility's retry option as it gets the size only once and does not update it when retrying.