Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
CURLOPT_FORBID_REUSE when multiplexing
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 5 Sep 2026 12:11:41 +0200 (CEST)
Hey all.
For decades libcurl has offered the CURLOPT_FORBID_REUSE option. When each
transfer uses a connection exclusively, it is easy to say and understand that
this option marks this as the last transfer on the connection. It cannot be
reused again for any further transfers.
When used for a transfer that is multiplexed together with other transfers
over the same connection, this option's meaning and functionality is unclear.
I propose we start by explicitly documenting the fact that this option has no
effect on multiplexed transfers to avoid surprising users.
See https://github.com/curl/curl/pull/22833
Thoughts?
Date: Sat, 5 Sep 2026 12:11:41 +0200 (CEST)
Hey all.
For decades libcurl has offered the CURLOPT_FORBID_REUSE option. When each
transfer uses a connection exclusively, it is easy to say and understand that
this option marks this as the last transfer on the connection. It cannot be
reused again for any further transfers.
When used for a transfer that is multiplexed together with other transfers
over the same connection, this option's meaning and functionality is unclear.
I propose we start by explicitly documenting the fact that this option has no
effect on multiplexed transfers to avoid surprising users.
See https://github.com/curl/curl/pull/22833
Thoughts?
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2026-09-05