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
net.http: honor peer SETTINGS_MAX_HEADER_LIST_SIZE on requests (RFC 9113 §6.5.2)
The sync and server paths recorded the peer advisory
SETTINGS_MAX_HEADER_LIST_SIZE but neither client path enforced it, and the
mux path did not even store it (apply_peer_settings had no arm for it, so it
was silently ignored). A request whose header list exceeded the server limit
was emitted and rejected only after the round trip.
Store the setting on the mux path (new wmu-guarded field + apply_peer_settings
arm, matching the sync/server paths) and, on both client paths, compute the
§6.5.2 header-list size (sum of name+value+32 per field) before encoding and
refuse an over-limit request locally with a non-retryable error (a fresh
connection to the same peer carries the same limit). Default is unlimited, so
behavior is unchanged unless the peer sets a limit. Adds tests on both paths.
Co-Authored-By: WOZCODE <contact@withwoz.com>
0 commit comments