Re: wget vs curl (was ... Re: debian 8)
On Sat, 4 Apr 2015 12:37:56 +1300
Chris Bannister <email@example.com> wrote:
> Come on guys, what's so difficult about trimming your posts.
> On Fri, Apr 03, 2015 at 08:22:11PM +0300, Reco wrote:
> > If it does not help - download the page with wget or curl (last one is
> > preferrable for this)
> What can curl do that wget can't do?
$ apt-get show wget | grep Dep
Depends: libc6 (>= 2.11), libgcrypt11 (>= 1.4.5), libgnutls26 (>= 2.12.17-0), libgpg-error0 (>= 1.10), libidn11 (>= 1.13), zlib1g (>= 1:1.1.4), dpkg (>= 1.15.4) | install-info
$ apt-get show curl | grep Dep
Depends: libc6 (>= 2.7), libcurl3 (= 7.26.0-1+wheezy12), zlib1g (>= 1:1.1.4)
$ apt-cache show libcurl3 | grep Dep
Depends: libc6 (>= 2.11), libgssapi-krb5-2 (>= 1.10+dfsg~), libidn11 (>= 1.13), libldap-2.4-2 (>= 2.4.7), librtmp0 (>= 2.3), libssh2-1 (>= 1.2.6), libssl1.0.0 (>= 1.0.1), zlib1g (>= 1:1.1.4)
It boils down to the fact that wget is linked against gnults and curl
is linked against openssl. Nothing that rebuild of a package can't
change, of course :)
And openssl is more tolerable to:
1) Self-signed certificates.
2) Mixed support of SSL3.0 and TLS1.0.
3) Disabled SSL3.0 and enabled TLS1.0 only.
Of those, only 3) somewhat applies to https://www.debian.org, but
people these days have really strange ideas of configuring TLS.
Especially if said people are allowed to configure web-servers.
So, in the case of doubt - you use curl or rebuild wget against
openssl. It's that simple.