)]}'
{
  "commit": "6e266113219cefe94bfb9c90fcac944748c4903f",
  "tree": "4b7462a03933f25c2aff0c10280cfdd7eb43edc2",
  "parents": [
    "e9be9e3f9fe6061c9185cb2eeafd7d0818399437"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Mar 23 16:52:23 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Mar 23 16:52:23 2021 +0300"
  },
  "message": "gRPC: fixed handling of padding on DATA frames.\n\nThe response size check introduced in 39501ce97e29 did not take into\naccount possible padding on DATA frames, resulting in incorrect\n\"upstream sent response body larger than indicated content length\" errors\nif upstream server used padding in responses with known length.\n\nFix is to check the actual size of response buffers produced by the code,\nsimilarly to how it is done in other protocols, instead of checking\nthe size of DATA frames.\n\nReported at:\nhttp://mailman.nginx.org/pipermail/nginx-devel/2021-March/013907.html\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f5bf575c2fb4dd703cf4e3d9ce0e24fc3e6e76df",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_grpc_module.c",
      "new_id": "53bc547102af6f8dc95834dbad2cb0e1d32079d2",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_grpc_module.c"
    }
  ]
}