)]}'
{
  "commit": "59f287ae4c7057ec0aa1ebf94e87ccb76247bddf",
  "tree": "10e4f33352cb32e0019a6eeccbfb1ec02e6486a7",
  "parents": [
    "9e05f769887baea31ed67d3f16ee6ae7b22d3370"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jan 24 17:18:50 2022 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon Jan 24 17:18:50 2022 +0300"
  },
  "message": "SSL: always renewing tickets with TLSv1.3 (ticket #1892).\n\nChrome only uses TLS session tickets once with TLS 1.3, likely following\nRFC 8446 Appendix C.4 recommendation.  With OpenSSL, this works fine with\nbuilt-in session tickets, since these are explicitly renewed in case of\nTLS 1.3 on each session reuse, but results in only two connections being\nreused after an initial handshake when using ssl_session_ticket_key.\n\nFix is to always renew TLS session tickets in case of TLS 1.3 when using\nssl_session_ticket_key, similarly to how it is done by OpenSSL internally.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "daa28ffe4db583e5e9cb48730c610713a92955a7",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_openssl.c",
      "new_id": "1e6fc961483bf31cc2008dae35f594f5dcb8fa27",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_openssl.c"
    }
  ]
}
