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 way it works right now, we aren't applying any settings until right as we send the ack. This can result in a race:
Server and client are in steady state with maximum streams = 5
Client receives a settings frame with a limit of 1. It appends the ack to the control buffer in response.
Client initiates 5 new streams and pushes their headers onto the control buffer, which it thinks is fine because the settings are not applied yet.
Client applies settings and sends settings ack, promising not to initiate more than one stream.
Client sends headers for 5 new streams.
We need to make sure settings are applied before queuing the ack message if the settings are more restrictive than they were before. On the other hand, we should queue the ack message and then apply the settings if they are more permissive.
The text was updated successfully, but these errors were encountered:
The way it works right now, we aren't applying any settings until right as we send the ack. This can result in a race:
We need to make sure settings are applied before queuing the ack message if the settings are more restrictive than they were before. On the other hand, we should queue the ack message and then apply the settings if they are more permissive.
The text was updated successfully, but these errors were encountered: