Re: Weird MAX_CONCURRENT_STREAMS value with empty HTTP/2 SETTINGS frame
Date: Fri, 5 Jun 2020 22:36:04 -0400
On 6/5/2020 12:09 PM, Daniel Stenberg via curl-users wrote:
> 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?
The default max concurrent streams in nghttp2 is 4294967295.