4 ms·

There is a setting in HTTP/2 called SETTINGS_MAX_CONCURRENT_STREAMS, if set to 1 it works like HTTP/1.1, with no multiplexing. Setting it to 4~8 would make it b

There is a setting in HTTP/2 called SETTINGS_MAX_CONCURRENT_STREAMS, if set to 1 it works like HTTP/1.1, with no multiplexing. Setting it to 4~8 would make it behave in a similar way a browser actually does with HTTP/1 (creating multiple connections in parallel).

j16sdiz 7y ago
This is a client side setting and default to 1000 in chrome. The http/1.1 equivalent was 8 or something like that.
- floatingatoll 7y ago
  While it is correct to say that it is a client setting, it is also a server setting. The HTTP/2 specification uses the word "peer" since SETTINGS_MAX_CONCURRENT_STREAMS (0x3) is negotiated in both directions as part of the client/server handshakes. $ nghttp -v https://www.google.com | grep -C5 SETTINGS_MAX_CONCURRENT_STREAMS [ 0.076] send SETTINGS frame <length=12, flags=0x00, stream_id=0> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100] [ 0.091] recv SETTINGS frame <length=18, flags=0x00, stream_id=0> [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
- ec109685 7y ago
  ALB clips this at 128: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-listeners.html https://docs.aws.amazon.com/elasticloadbalancing/latest/appl...