)]}'
{
  "commit": "c446fc2d1c1ce3ae18b4ec9f070e8cf9a18ff438",
  "tree": "5e958ea51ce2d12acbec063a3f89a3b90f5b413b",
  "parents": [
    "c685ea43400584dfe265c34cdb65cb036a1f6003"
  ],
  "author": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Apr 14 15:14:15 2016 +0300"
  },
  "committer": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Apr 14 15:14:15 2016 +0300"
  },
  "message": "HTTP/2: send WINDOW_UPDATE instead of RST_STREAM with NO_ERROR.\n\nAfter the 92464ebace8e change, it has been discovered that not all\nclients follow the RFC and handle RST_STREAM with NO_ERROR properly.\n\nNotably, Chrome currently interprets it as INTERNAL_ERROR and discards\nthe response.\n\nAs a workaround, instead of RST_STREAM the maximum stream window update\nwill be sent, which will let client to send up to 2 GB of a request body\ndata before getting stuck on flow control.  All the received data will\nbe silently discarded.\n\nSee for details:\nhttp://mailman.nginx.org/pipermail/nginx-devel/2016-April/008143.html\nhttps://bugs.chromium.org/p/chromium/issues/detail?id\u003d603182\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "74754977b661340708a8da530a9d5aad2dce1b42",
      "old_mode": 33188,
      "old_path": "src/http/v2/ngx_http_v2.c",
      "new_id": "c88e29728a4e2c693dae0ae135dc72601a8b08e2",
      "new_mode": 33188,
      "new_path": "src/http/v2/ngx_http_v2.c"
    }
  ]
}