)]}'
{
  "commit": "97246de8b6bc75232729dd06e040a39409a5fac4",
  "tree": "34bc04caeccbc47691252f39347b238bb85e3070",
  "parents": [
    "efb64f89bbb14352d9a28f4cda43907ffeddf0f9"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Sep 11 17:04:04 2015 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Sep 11 17:04:04 2015 +0300"
  },
  "message": "Fixed segfault with incorrect location nesting.\n\nA configuration with a named location inside a zero-length prefix\nor regex location used to trigger a segmentation fault, as\nngx_http_core_location() failed to properly detect if a nested location\nwas created.  Example configuration to reproduce the problem:\n\n    location \"\" {\n        location @foo {}\n    }\n\nFix is to not rely on a parent location name length, but rather check\ncommand type we are currently parsing.\n\nIdentical fix is also applied to ngx_http_rewrite_if(), which used to\nincorrectly assume the \"if\" directive is on server{} level in such\nlocations.\n\nReported by Markus Linnala.\nFound with afl-fuzz.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f24119645bbf1f96099ecf4e3ac66b8be1994b4e",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_rewrite_module.c",
      "new_id": "754512fb1930c64f0a44c91f226e1e439ea65bf2",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_rewrite_module.c"
    },
    {
      "type": "modify",
      "old_id": "0a5b6b47b74bfec20190ab9af949cd6cb553c629",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_core_module.c",
      "new_id": "5cdf9873b5348c9b3e4fabce2487c227ee54ba1f",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_core_module.c"
    }
  ]
}