)]}'
{
  "commit": "aae040e70e01a76b125384b2b27c84c37199fd31",
  "tree": "1d9506ada08cd086c75fd84ab680d1a90f37f675",
  "parents": [
    "e484a9ccfcf53b82785cc719494b086b9a8742af"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Feb 28 17:21:18 2020 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Feb 28 17:21:18 2020 +0300"
  },
  "message": "Added default overwrite in error_page 494.\n\nWe used to have default error_page overwrite for 495, 496, and 497, so\na configuration like\n\n    error_page 495 /error;\n\nwill result in error 400, much like without any error_page configured.\n\nThe 494 status code was introduced later (in 3848:de59ad6bf557, nginx 0.9.4),\nand relevant changes to ngx_http_core_error_page() were missed, resulting\nin inconsistent behaviour of \"error_page 494\" - with error_page configured\nit results in 494 being returned instead of 400.\n\nReported by Frank Liu,\nhttp://mailman.nginx.org/pipermail/nginx/2020-February/058957.html.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "da23af1fbfc6765e60e54f9904a70b989b7b5646",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_core_module.c",
      "new_id": "4867bed2b37c61307e06cc68ecd67c16b059ac21",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_core_module.c"
    }
  ]
}