Re: CURLOPT_PROTOCOLS_STR man page

Daniel Stenberg via curl-library <[email protected]> Wed, 17 Jun 2026 09:30:45 +0200 (CEST)
Newsgroups gmane.comp.web.curl.library
Message-ID <[email protected]>
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---39887073-280149436-1781681445=:2569524
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Sun, 14 Jun 2026, dogma via curl-library wrote:

> I specify "http,https,file", thinking to be more secure when I’m not doing 
> anything useful with the other schemes anyway 
> (https://curl.se/libcurl/security.html showing how nasty a protocol such as 
> scp can be). A user configures libcurl to disable "http". The call fails and 
> I haven’t accomplished anything.

If you set the protocols you need your application to use, then a failure 
means that you can't continue!

> I guess I have to consult the protocol list out of curl_version_info() as I 
> construct my string?

If you really want to adjust to crazy custom libcurl builds, yes.

-- 

  / daniel.haxx.se || https://rock-solid.curl.dev
---39887073-280149436-1781681445=:2569524
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

---39887073-280149436-1781681445=:2569524--