)]}'
{
  "commit": "fbd3e2cc9bdbf2a1a78f23f0456f8eebf215ba06",
  "tree": "ac10d03186a1b35eea38aedef8b32e35f4ed9376",
  "parents": [
    "32a0ca8b35830b69144dc8dcadc7ffe5539390ae"
  ],
  "author": {
    "name": "yhirose",
    "email": "yuji.hirose.bug@gmail.com",
    "time": "Thu Oct 22 07:58:28 2026 -0400"
  },
  "committer": {
    "name": "yhirose",
    "email": "yuji.hirose.bug@gmail.com",
    "time": "Thu Oct 22 07:58:28 2026 -0400"
  },
  "message": "Answer 501 to a request with a transfer coding besides chunked\n\nA request whose Transfer-Encoding ended in chunked but listed more\n(another coding before chunked, or chunked twice) was read with only\nthe chunked framing removed, so the handler got a body still in the\nother coding. RFC 9112 6.1 lets a server answer 501 to a transfer\ncoding it does not implement. The server now accepts only a single\nTransfer-Encoding field whose value is chunked, as Go and nginx do,\nand answers any other list ending in chunked with 501 and closes the\nconnection. A list whose final coding is not chunked still gets 400.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b23bfa0a9aa740892db9bd03696f999f3a852a76",
      "old_mode": 33188,
      "old_path": "httplib.h",
      "new_id": "44e3d1a102e611366962db6b7dbd4831867c44ec",
      "new_mode": 33188,
      "new_path": "httplib.h"
    },
    {
      "type": "modify",
      "old_id": "32c2089c9d97f2dd0bb4698d546a1f2662c7bd46",
      "old_mode": 33188,
      "old_path": "test/test.cc",
      "new_id": "fb87a2f906a927a987dc23d9089794225bbe3611",
      "new_mode": 33188,
      "new_path": "test/test.cc"
    }
  ]
}