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: Weird MAX_CONCURRENT_STREAMS value with empty HTTP/2 SETTINGS frame
From: Daniel Stenberg via curl-users <curl-users_at_cool.haxx.se>
Date: Fri, 5 Jun 2020 18:09:36 +0200 (CEST)
Date: Fri, 5 Jun 2020 18:09:36 +0200 (CEST)
On Fri, 5 Jun 2020, Alexandre Pion via curl-users wrote:
> I was looking for MAX_CONCURRENT_STREAMS SETTINGS value with curl and it
> appears that when receiving an empty SETTINGS frame curl says the server
> announced 4294967295 MAX_CONCURRENT_STREAMS. Is this a normal behavior ?
No it isn't.
Seems like it might be a nghttp2 issue though, as it tells curl there's a
settings frame and the curl code simply reads what nghttp2 told it...
Is this reproducible against a public site?
--
/ 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-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-06-05