)]}'
{
  "commit": "f832b67df4cc1d47b40bca1dbb69336d1178a645",
  "tree": "d3f1c433c7a65a55220c42d8ed064561d00306cf",
  "parents": [
    "717df913ea56c4c372895eb9c2dbdb9a1fa383f9"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Oct 29 20:21:48 2021 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Fri Oct 29 20:21:48 2021 +0300"
  },
  "message": "Simplified sendfile_max_chunk handling.\n\nPreviously, it was checked that sendfile_max_chunk was enabled and\nalmost whole sendfile_max_chunk was sent (see e67ef50c3176), to avoid\ndelaying connections where sendfile_max_chunk wasn\u0027t reached (for example,\nwhen sending responses smaller than sendfile_max_chunk).  Now we instead\ncheck if there are unsent data, and the connection is still ready for writing.\nAdditionally we also check c-\u003ewrite-\u003edelayed to ignore connections already\ndelayed by limit_rate.\n\nThis approach is believed to be more robust, and correctly handles\nnot only sendfile_max_chunk, but also internal limits of c-\u003esend_chain(),\nsuch as sendfile() maximum supported length (ticket #1870).\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bd37704578119789052e57f713c9c909d17a9888",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_write_filter_module.c",
      "new_id": "932f26dd3055c5da5f173aa1e0bcfc40db27895c",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_write_filter_module.c"
    }
  ]
}