On Tue, 10 Mar 2020, Dima Tisnek via curl-library wrote:
The connection is (and must be) http/2 with client cert.
Really? I thought client certs were explicitly not permitted with HTTP/2
without going the Secondary Certificate Authentication route - which is still
a draft spec but more importantly one that curl doesn't implement.
I get a weird endless retry from curl, one cycle of the retry looks like this:
* Connection state changed (MAX_CONCURRENT_STREAMS == 1234567890)!
That's a lot of concurrent streams!
* REFUSED_STREAM, retrying a fresh connect
* Connection died, retrying a fresh connect
* Closing connection 988
...
But it's also quite so weird that curl just doesn't give up and tries
again and again and again...
Yeah, there needs to be a loop prevention thing there. I'll look into it!
--
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
