Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: HTTP/2 and multi-streams
From: Daniel Stenberg via curl-and-python <curl-and-python_at_cool.haxx.se>
Date: Sun, 19 Jan 2020 17:51:01 +0100 (CET)
Date: Sun, 19 Jan 2020 17:51:01 +0100 (CET)
On Sun, 19 Jan 2020, Stephane Bortzmeyer wrote:
> m.setopt(m.M_MAX_HOST_CONNECTIONS, 1) # Python
>
> to see the use of several HTTP/2 streams per connection:
>
> % ./test-multi-wait |& grep Stream
> * Using Stream ID: 1 (easy handle 0x1415818)
> * Using Stream ID: 3 (easy handle 0x141a7d0)
>
> (Success, two different streams.)
This is probably because of my stupidity. There's a regression in libcurl
since 7.65.0 that wasn't fixed until *after* 7.68.0 was released (to be
included in the future 7.69.0 release), that makes it prefer new connections
instead of new streams far too much in the default case.
(Fixed here: https://github.com/curl/curl/pull/4784)
--
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
| https://www.wolfssl.com/contact/
_______________________________________________
https://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python
Received on 2020-01-19