You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server_max_window_bits value sent by the client in the negotiation
offer is used to configure the deflater on the server. This acceptance
is also notified to the client by returning the server_max_window_bits
header in the negotiation response.
A special case arises when we receive server_max_window_bits = 8.
There's an open zlib issue with the window size of 8. For zlib
streams, the library silently changes the window size to 9 and informs
the inflater via the zlib header. However, this apparent hack is not
feasible for raw deflate streams, which are used in WebSockets. To
take care of this fact, zlib has been patched to reject a window size
of 8, via a deflateInit2() failure.
Details here: madler/zlib#171
As a result, we need to handle a window size request of 8 as a special
case. We silently change it to 9 and inform the client via a suitable
header in the negotiation response.
0 commit comments