mirror of
https://github.com/haproxy/haproxy.git
synced 2026-05-21 01:15:17 -04:00
d21ec4c707
When stream elasticity is active, the maximum number of concurrent bidi streams advertised via transport parameters is now reduced depending on the connection load. This is implemented via conn_calc_max_streams() which returns the value to use. This is not applied on listeners with enabled 0-RTT. Indeed, for such connections, clients are expected to reuse the previously seen transport parameters. The server on the other hand must not decrease several values on the newly advertised params, in particular for the maximum number of concurrent bidi streams. The simplest way to prevent 0-RTT failure is to not mix stream elasticity with it. Note that the 0-RTT limitation is only applied for the initial value : during the connection lifetime, stream elasticity can still be used by the MUX to dynamically reduce the stream window. This will be implemented in a future patch. |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| lua-api | ||
| 51Degrees-device-detection.txt | ||
| acl.fig | ||
| coding-style.txt | ||
| configuration.txt | ||
| cookie-options.txt | ||
| DeviceAtlas-device-detection.txt | ||
| gpl.txt | ||
| haproxy.1 | ||
| HAProxyCommunityEdition_60px.png | ||
| haterm.txt | ||
| intro.txt | ||
| lgpl.txt | ||
| linux-syn-cookies.txt | ||
| lua.txt | ||
| management.txt | ||
| netscaler-client-ip-insertion-protocol.txt | ||
| network-namespaces.txt | ||
| peers-v2.0.txt | ||
| peers.txt | ||
| proxy-protocol.txt | ||
| queuing.fig | ||
| regression-testing.txt | ||
| seamless_reload.txt | ||
| SOCKS4.protocol.txt | ||
| SPOE.txt | ||
| WURFL-device-detection.txt | ||
