tree 73f66c50b2c7f6af41e362d4a1f0a69a2a72d105
parent 0b5e445de64c22251a35a8b1c805e0d5723fca94
author QUICHE team <quiche-dev@google.com> 1750725647 -0700
committer Copybara-Service <copybara-worker@google.com> 1750725698 -0700

Fix Known-Length BHTTP frame decoding

The current logic assumes the framing indicator is only one byte, but [RFC 9292](https://www.rfc-editor.org/rfc/rfc9292.html) states that the request and response framing indicators use the variable-length integer encoding from [RFC 9000](https://www.rfc-editor.org/rfc/rfc9000#section-16) and that values do not need to be encoded on the minimum number of bytes necessary. This means the logic has to also handle 2, 4, and 8-byte long values.

Protected by Tests, this change still handles the 1-byte framing indicator.

PiperOrigin-RevId: 774991715