)]}'
{
  "commit": "cf7b9a61485df99f526718cf84559a0bbadaaf11",
  "tree": "9e0978cb306a8ef051cea2d63b9218f5e28fc66f",
  "parents": [
    "873ebaf43cfa399cda52ee0454b97328c6bde587"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon May 13 22:44:02 2019 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Mon May 13 22:44:02 2019 +0300"
  },
  "message": "Range filter: fixed loss of incoming chain links.\n\nFilters are not allowed to change incoming chain links, and should allocate\ntheir own links if any modifications are needed.  Nevertheless\nngx_http_range_singlepart_body() modified incoming chain links in some\ncases, notably at the end of the requested range.\n\nNo problems caused by this are currently known, mostly because of\nlimited number of possible modifications and the position of the range\nbody filter in the filter chain.  Though this behaviour is clearly incorrect\nand tests demonstrate that it can at least cause some proxy buffers being\nlost when using proxy_force_ranges, leading to less effective handling\nof responses.\n\nFix is to always allocate new chain links in ngx_http_range_singlepart_body().\nLinks are explicitly freed to ensure constant memory usage with long-lived\nrequests.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "819c5c9429496510034a3fdca7c84a8f61b3fd46",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_range_filter_module.c",
      "new_id": "8dd07205a1053740ce85a34da349634d3a929e3c",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_range_filter_module.c"
    }
  ]
}
