Hi All,
As H3 in libcurl is going steadily to the production feature, I would like to
tell about one H3/QUIC issue, which was OK for the experimental stage, but
probably needs to be addressed to make H3 a full production feature.
When I was comparing H3/QUIC with the H1/H2 TCP in my local
On 1/6/23 18:44, Calvin Buckley via curl-library wrote:
On Tue, 2023-01-03 at 20:07 +, Sam James wrote:
Apologies for the late reply. I forgot to subscribe to the list when I
sent this, so my mail got eaten for the public list (sorry you'll be
receiving this one again Daniel!), but I took
On Fri, Jan 06, 2023 at 01:44:48PM -0400, Calvin Buckley via curl-library wrote:
> - I have capacity on a shared system intended for open source
> development. I should be able to set up some kind of CI runner here.
> The very annoying part is Go isn't supported (bar an experimental
>
On Tue, 2023-01-03 at 20:07 +, Sam James wrote:
> CCing Calvin who has a strong interest in this and might be able to
> coordinate something. He's not sub'd.
>
> Best,
> sam
Apologies for the late reply. I forgot to subscribe to the list when I
sent this, so my mail got eaten for the public
On Thu, 5 Jan 2023, Jeroen Ooms via curl-library wrote:
However the documentation says CURLSSLOPT_NATIVE_CA (introduced in
7.71.0) is experimental and subject to change. Is it safe to use at
this point?
I think we should consider removing the experimental label for this.
This is hard for us
