HTTP/2 Concurrent streams question

Michael McMahon michael.x.mcmahon at
Wed Nov 7 10:44:03 UTC 2018


This is the right place to ask! It was implemented that way because RFC 7540
recommends that:

    Clients SHOULD NOT open more than one HTTP/2 connection to a given
    host and port pair, where the host is derived from a URI, a selected
    alternative service [ALT-SVC  <>], or a configured proxy.

One workaround would be to create a second HttpClient in that situation.
As a matter of interest, what limit is imposed by the server in this case?


On 07/11/2018, 10:22, Elias Schulze wrote:
> Hi!
> Not sure if this is the right place to ask, please point me in the 
> right direction if it's not. My question is regarding the IOException 
> "too many concurrent streams" in Http2Connection line 440. Probably my 
> understanding of HTTP/2 and net.http is wrong, but I expected the 
> HttpClient to open new parallel connections if the max concurrent 
> streams is reached for any one open connection and there's more 
> request to be sent. Why doesn't it? Am I meant to handle such cases 
> myself? The server in this case is an amazon load balancer, so I can't 
> change the server HTTP/2 settings.
> Thanks in advance!
> Elias
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the net-dev mailing list