randomize the serialization order of control frames #4069
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently discovered a bug where the receiver relied on frames being sent in a particular order. This PR randomizes the order of what we call control frames (all frames other than ACK or STREAM frames) when packing the packet.
I'd like to randomize the order of the ACK as well (currently it's always serialized first). We could do this, but we wouldn't have a way to (q)log this without changing the tracer call, so this would be a bigger change:
quic-go/logging/interface.go
Line 117 in 591d864