curl is probably a tiny bit more assured to be available than wget, and it executes a bit faster, at least on all Debian versions I tested. With the used flags, the behaviour of the previous wget call is maintained:
-s/--silence mutes all output
-S/--show-error shows error messages despite -s/--silence is used
-f/--fail assures that 40x HTML documents, possibly returned by the webserver, are not downloaded but the response code printed as error message with curl returning an error exit code
-L/--location follows redirects: Actually not required here, could be skipped?
-O/--remote-name downloads the document into a name matching the name in the request URL
This is really just a minor suggestion. I just ran into a failure since I always use curl and have wget not installed on my testing VMs 😉.
curlis probably a tiny bit more assured to be available thanwget, and it executes a bit faster, at least on all Debian versions I tested. With the used flags, the behaviour of the previouswgetcall is maintained:-s/--silencemutes all output-S/--show-errorshows error messages despite-s/--silenceis used-f/--failassures that 40x HTML documents, possibly returned by the webserver, are not downloaded but the response code printed as error message withcurlreturning an error exit code-L/--locationfollows redirects: Actually not required here, could be skipped?-O/--remote-namedownloads the document into a name matching the name in the request URLThis is really just a minor suggestion. I just ran into a failure since I always use
curland havewgetnot installed on my testing VMs 😉.