Stefan Eissing

`curl: (43) A libcurl function was given a bad argument` looks strange. I do not see that on my dev build on macOS. If you indeed have a 8.4 curl...

@jay the eyeballing in QUIC always involves a new TLS instance for every connection. That is why it is showing the messages. I doubt we can avoid that. We *could*...

This looks as if it would block until the SSL stack is actually able to send the close notify. If the outgoing socket is "full", EGAIN is returned. SSL would...

Could you check if #11858 helps with the shutdown problems? UPDATE: sorry, #11858 isn't yet in the state it should be. I'll update when done. UPDATE: now it's in a...

Added some debug info's to this. I see that in `Curl_hyper_stream()`which is called by curl's transfer loop: 1. socket gives POLLIN event 2. Curl_hyper_stream() is called 3. `hyper_waker_wake(h->read_waker)` is called...

@gvanem you are right. I wanted to document my observations to drag the hyper project in. I think this is a bug on their behalf, but if the insist everything...

Opened https://github.com/hyperium/hyper/issues/3237

On advisement of @seanmonstar I made some small changes that resolve the slowness for me. Pr in #11344. I see our http/1.1 test cases work, h2 has issues with connection...

@gvanem can you inspect/dump the values of that assertion failure?

hmm, a 64bit -1 as unsigned. but the var `nread` is an `ssize_t`. How could that happen in: ``` ssize_t nread; CF_DATA_SAVE(save, cf, data); *err = CURLE_OK; nread = Curl_ssl->recv_plain(cf,...