[I] `Http3FrameDispatcher` counts sequence numbers incorrectly [trafficserver]

["JosiahWI (via GitHub)" <gi...@apache.org>]

JosiahWI opened a new issue, #11622:
URL: https://github.com/apache/trafficserver/issues/11622

   They are *mostly* counted correctly, but there is a case that isn't. This can be reproduced by adding a protocol enforcer to the "padding should not be interpreted as a data frame" test in test_Http3FrameDispatcher.cc.
   
   ```cpp
     uint8_t input[] = {
       0x40, 0x04, // Type
       0x03,       // Length
       0x06,       // Identifier
       0x44, 0x00, // Value
     };
   ```
   
   This gets read in one byte at a time; if read all at once, the bug doesn't manifest. The padding byte in the frame type causes something to be miscounted, and the protocol enforcer will get called with a sequence number of `-1`.  Because this is a SETTINGS  frame on a CONTROL stream and the sequence number isn't 0, it generates an `H3_FRAME_UNEXPECTED` error.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] `Http3FrameDispatcher` counts sequence numbers incorrectly [trafficserver]

["maskit (via GitHub)" <gi...@apache.org>]

maskit closed issue #11622: `Http3FrameDispatcher` counts sequence numbers incorrectly
URL: https://github.com/apache/trafficserver/issues/11622


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org