Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
man pages: switch to https://example.com URLs #5969
A no vote from me. TLS support is not compiled by default, only if such a library is found on the system. Also it can lead to many issues like invalid certificates...
Don't get me wrong and think I am not a fan of HTTPS, I just tjink it's too much overkill for an example. Also it would more or less add an external dependeny required for it
With "the new normal" I mean that HTTPS is the most commonly used protocol for users to use with curl, and it is by far the most commonly used protocol in browsers and when showing links in general today (in print, on a site, in an email etc).
There's virtually no users around anymore who build curl with HTTP support but without HTTPS. I don't see how it is "overkill" for an example since it just changes the URL string with an added
The examples in the man pages are only very small snippets showing how to use a particular option, they're not complete stand-alone apps. Besides, certificate validation is enabled by default and for most users it should work exactly as intended without any additional options.
Exactly how would this make anything better for anyone? It also seems unrelated to this change...