On Wed, 4 Jan 2023, Stefan Eissing wrote:
Would
--proto h3,h2
--proto http3,http2
--proto http1-3
work here?
Sure! If we want to overload that option with this information and consider
http3, http2 and http1 to be "protocols" I believe we can.
What might be a little confusing to user with that is that it already accepts
"http" and "https" as different protocols (schemes really) while "httpN"
affects the version used over both those schemes (http1 for both, http2 for
both, http3 only for https). Probably not a blocker.
I believe it could offer the flexibility we want as this also allows - and +
to exclude/include only specific choices from/to the default set.
The follow-up question is then of course how exactly that would map into one
or more libcurl option(s).
--
/ daniel.haxx.se
| Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://curl.se/support.html
--
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
