Bug #4228
closed
tcp/async: incorrect flagging of ACK values as invalid
Added by Victor Julien about 4 years ago.
Updated almost 4 years ago.
Description
In an async session where we only see the toclient side, the `next_win` is not properly initialized leading to invalid ack events for correct ACKs.
- Copied to Bug #4229: tcp/async: incorrect flagging of ACK values as invalid added
- Copied to Bug #4230: tcp/async: incorrect flagging of ACK values as invalid added
- Status changed from Assigned to In Review
- Status changed from In Review to Closed
- Label deleted (
Needs backport to 5.0, Needs backport to 6.0)
Also available in: Atom
PDF