0012f899dd
This changes the default from RFC 7540's default 65535 (64k-1) to avoid avoid some degenerative WINDOW_UPDATE behaviors in the wild observed with clients using 65536 as their buffer size, and have to complete each block with a 1-byte frame, which with some servers tend to degenerate in 1-byte WU causing more 1-byte frames to be sent until the transfer almost only uses 1-byte frames. More details here: https://github.com/nghttp2/nghttp2/issues/1722 As mentioned in previous commit (MEDIUM: mux-h2: try to coalesce outgoing WINDOW_UPDATE frames) the issue could not be reproduced with haproxy but individual WU frames are sent so theoretically nothing prevents this from happening. As such it should be backported as a workaround for already deployed clients after watching for any possible side effect with rare clients. As an added benefit, uploads from curl now use less DATA frames (all are 16384 now). Note that the previous patch alone is sufficient to stop the issue with curl in case this one would need to be reverted. [wt: edited commit messaged, updated doc] |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| lua-api | ||
| 51Degrees-device-detection.txt | ||
| DeviceAtlas-device-detection.txt | ||
| SOCKS4.protocol.txt | ||
| SPOE.txt | ||
| WURFL-device-detection.txt | ||
| acl.fig | ||
| architecture.txt | ||
| close-options.txt | ||
| coding-style.txt | ||
| configuration.txt | ||
| cookie-options.txt | ||
| gpl.txt | ||
| haproxy.1 | ||
| 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 | ||