)]}'
{
  "commit": "8a11d4aa62a24ba6be527258ee5536c3270a13cc",
  "tree": "b0a01db06825a92bf1fee49495fce0c3ea48cc8c",
  "parents": [
    "5adc699f204d7fdfa6a229ca765d2611329eeaaa"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon May 30 21:25:56 2022 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon May 30 21:25:56 2022 +0300"
  },
  "message": "Multiple WWW-Authenticate headers with \"satisfy any;\".\n\nIf a module adds multiple WWW-Authenticate headers (ticket #485) to the\nresponse, linked in r-\u003eheaders_out.www_authenticate, all headers are now\ncleared if another module later allows access.\n\nThis change is a nop for standard modules, since the only access module which\ncan add multiple WWW-Authenticate headers is the auth request module, and\nit is checked after other standard access modules.  Though this might\naffect some third party access modules.\n\nNote that if a 3rd party module adds a single WWW-Authenticate header\nand not yet modified to set the header\u0027s next pointer to NULL, attempt to\nclear such a header with this change will result in a segmentation fault.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0c7dd3f99349eb37ab755f95d6f2a7e6e2938eb9",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_core_module.c",
      "new_id": "28f7d99b455fe3c26b40029a0133608e1d772faf",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_core_module.c"
    }
  ]
}