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
On Wed, 4 Jan 2023, Samuel Hurst via curl-library wrote:
I was just about to post on the subject of DNS service binding [1] for
discovering h3. Although given there's no current interface for discovering
SVCB records via getaddrinfo, is this more a discussion for c-ares? What
implications
On 04/01/2023 10:04, Stefan Eissing via curl-library wrote:>> Am
04.01.2023 um 10:50 schrieb Daniel Stenberg :
On Wed, 4 Jan 2023, Stefan Eissing wrote:
And then there are the cases where someone really wants to nail it down. That is what we
are talking here, I guess. Ultimately, what is given
> Am 04.01.2023 um 10:50 schrieb Daniel Stenberg :
>
> On Wed, 4 Jan 2023, Stefan Eissing wrote:
>
>> And then there are the cases where someone really wants to nail it down.
>> That is what we are talking here, I guess. Ultimately, what is given on the
>> command line is converted by curl
On Wed, 4 Jan 2023, Stefan Eissing wrote:
And then there are the cases where someone really wants to nail it down.
That is what we are talking here, I guess. Ultimately, what is given on the
command line is converted by curl into TCP and/or QUIC and the ALPN list for
the connection (ignoring
> Am 04.01.2023 um 09:08 schrieb Daniel Stenberg via curl-library
> :
>
> On Tue, 3 Jan 2023, Timothe Litt via curl-library wrote:
>
> Thanks, this is certainly an interesting idea.
>
>> --http=3 - use http3, fall back to 2, 1.1, 1.0, 0.9, ...
>
> We don't use '='-separators in our option
On Tue, 3 Jan 2023, Timothe Litt via curl-library wrote:
Thanks, this is certainly an interesting idea.
--http=3 - use http3, fall back to 2, 1.1, 1.0, 0.9, ...
We don't use '='-separators in our option parser so unless we introduce it
now, it would rather be
--http 3
"0.9" is never a
