)]}'
{
  "commit": "1a82c3c7ef44670191c5dee9511f4ab9f02cce64",
  "tree": "73f66c50b2c7f6af41e362d4a1f0a69a2a72d105",
  "parents": [
    "0b5e445de64c22251a35a8b1c805e0d5723fca94"
  ],
  "author": {
    "name": "QUICHE team",
    "email": "quiche-dev@google.com",
    "time": "Mon Jun 23 17:40:47 2025 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Mon Jun 23 17:41:38 2025 -0700"
  },
  "message": "Fix Known-Length BHTTP frame decoding\n\nThe 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.\n\nProtected by Tests, this change still handles the 1-byte framing indicator.\n\nPiperOrigin-RevId: 774991715\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cf95e345072fba0ce5aedcfed2a661d530a28e85",
      "old_mode": 33188,
      "old_path": "quiche/binary_http/binary_http_message.cc",
      "new_id": "815b30efc479a6aec842cc5116aa397b1f2521ac",
      "new_mode": 33188,
      "new_path": "quiche/binary_http/binary_http_message.cc"
    },
    {
      "type": "modify",
      "old_id": "5841b2ab4bc951d2e3cf0f180b42e9fda59fa59e",
      "old_mode": 33188,
      "old_path": "quiche/binary_http/binary_http_message_test.cc",
      "new_id": "0ae8e883b2f562388be389226857d59e795a3c4b",
      "new_mode": 33188,
      "new_path": "quiche/binary_http/binary_http_message_test.cc"
    }
  ]
}