Re: CURLOPT_PROTOCOLS_STR man page

Daniel Stenberg via curl-library <[email protected]> Sun, 14 Jun 2026 22:14:38 +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-1490843243-1781468078=:2968776
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

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

> The man page gives me the impression that if CURLE_UNSUPPORTED_PROTOCOL is 
> returned, CURLOPT_PROTOCOLS_STR probably didn’t change anything.
>
> But I found that passing it, e.g., "http,https,unrecognized" made it 
> complain about unrecognized but it did change the allowed protocols to http 
> and https, as I was hoping.

You did not say which libcurl version you're using, but looking at the current 
code I cannot see it working like you describe. A single bad protocol in the 
input list will cause it to return error and leave the setting in its previous 
state.

-- 

  / daniel.haxx.se || https://rock-solid.curl.dev
---39887073-1490843243-1781468078=:2968776
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-1490843243-1781468078=:2968776--