Sujet : Re: Need Assistance -- Network Programming
De : candycanearter07 (at) *nospam* candycanearter07.nomail.afraid (candycanearter07)
Groupes : comp.os.linux.advocacyDate : 26. Jun 2024, 08:40:02
Autres entêtes
Organisation : the-candyden-of-code
Message-ID : <slrnv7nddu.21cs.candycanearter07@candydeb.host.invalid>
References : 1 2 3 4 5 6
User-Agent : slrn/1.0.3 (Linux)
Lawrence D'Oliveiro <
ldo@nz.invalid> wrote at 02:54 this Wednesday (GMT):
On 22 Jun 2024 09:37:37 GMT, Stéphane CARPENTIER wrote:
>
Yes, it's impressive to discover he never heard about wget or curl.
>
I prefer wget to curl. curl includes client code for something like two
dozen different protocols, and that just adds to the potential for
security vulnerabilities, particularly when all those extra protocols
already have perfectly good clients of their own.
>
wget, by contrast, concentrates on the basics: HTTP/HTTPS/FTP/FTPS. And
that’s it.
I'll be honest, I use both somewhat interchangeably. I know that you can
set the output file with -o in wget, but I still kinda prefer doing
curl url > file when I want it to be named something.
Also, hot tip: --content-disposition is great on some websites when
using wget, since otherwise it just saves it as the url basepath. Really
useful sometimes.
-- user <candycane> is generated from /dev/urandom