)]}'
{
  "commit": "ab8b107e0f47c29967c0b0fc53eef1d9489b39bf",
  "tree": "ccbad227be9d94f0c760fac61b460655837e380a",
  "parents": [
    "7546b8be84381ab40eb2025d8161342edd76c235"
  ],
  "author": {
    "name": "Sergey Kandaurov",
    "email": "pluknet@nginx.com",
    "time": "Tue Feb 08 17:35:27 2022 +0300"
  },
  "committer": {
    "name": "Sergey Kandaurov",
    "email": "pluknet@nginx.com",
    "time": "Tue Feb 08 17:35:27 2022 +0300"
  },
  "message": "SSL: logging level of \"application data after close notify\".\n\nSuch fatal errors are reported by OpenSSL 1.1.1, and similarly by BoringSSL,\nif application data is encountered during SSL shutdown, which started to be\nobserved on the second SSL_shutdown() call after SSL shutdown fixes made in\n09fb2135a589 (1.19.2).  The error means that the client continues to send\napplication data after receiving the \"close_notify\" alert (ticket #2318).\nPreviously it was reported as SSL_shutdown() error of SSL_ERROR_SYSCALL.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1e6fc961483bf31cc2008dae35f594f5dcb8fa27",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_openssl.c",
      "new_id": "975f959ac482633161f8849bc1e2ede608ed4ec8",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_openssl.c"
    }
  ]
}