)]}'
{
  "commit": "ae2161f4650b1796fe8f7d1fe35738e8d4a788e6",
  "tree": "89969990216c0f46534bc562d449648ca7c4b99b",
  "parents": [
    "ffc3f1bdbd8654e78e59a94330cce0e3e47ea6a3"
  ],
  "author": {
    "name": "apaseltiner",
    "email": "apaseltiner@google.com",
    "time": "Tue Sep 29 09:12:35 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Tue Sep 29 09:13:46 2026 -0700"
  },
  "message": "Reject leading asterisks on tokens in Draft 09 structured headers.\n\nDraft 09 of the Structured Headers specification (Section 3.9 and Section 4.2.10) requires tokens to begin with an alphabetic character, whereas RFC 8941 (Section 3.3.4) also permits a leading asterisk. Previously, `StructuredHeaderParser::ReadToken` unconditionally allowed a leading asterisk regardless of the parser version, which caused `ParseParameterisedList` to erroneously accept primary identifiers starting with an asterisk.\n\nRestrict leading asterisks in `ReadToken` to `kFinal` (RFC 8941).\n\nPiperOrigin-RevId: 990346076\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "572e8a8af6d9c0706cd16a0709731316246fc0ce",
      "old_mode": 33188,
      "old_path": "quiche/common/structured_headers.cc",
      "new_id": "65ef30cd49a7386334f5b0e5f464d3df9dda9d35",
      "new_mode": 33188,
      "new_path": "quiche/common/structured_headers.cc"
    },
    {
      "type": "modify",
      "old_id": "dc0ed3cc8b17dadb28f4bf55e5274b8d5df547d9",
      "old_mode": 33188,
      "old_path": "quiche/common/structured_headers_test.cc",
      "new_id": "84f13ffef61f20bcadcd3a8b94fcf07416edba34",
      "new_mode": 33188,
      "new_path": "quiche/common/structured_headers_test.cc"
    }
  ]
}