)]}'
{
  "commit": "b011293c4b385c956b3390e1b66e1bf2cc19b9f1",
  "tree": "a09cfd4c3a9ce4420dc90bce53603c305e23dfc6",
  "parents": [
    "2da47d81c38124dbf2cd1c2472990728cde4a6f2"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Jun 27 00:53:46 2017 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Jun 27 00:53:46 2017 +0300"
  },
  "message": "Range filter: allowed ranges on empty files (ticket #1031).\n\nAs per RFC 2616 / RFC 7233, any range request to an empty file\nis expected to result in 416 Range Not Satisfiable response, as\nthere cannot be a \"byte-range-spec whose first-byte-pos is less\nthan the current length of the entity-body\".  On the other hand,\nthis makes use of byte-range requests inconvenient in some cases,\nas reported for the slice module here:\n\nhttp://mailman.nginx.org/pipermail/nginx-devel/2017-June/010177.html\n\nThis commit changes range filter to instead return 200 if the file\nis empty and the range requested starts at 0.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8ffca82e64f8378f743bf425f4a74bab76b8b166",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_range_filter_module.c",
      "new_id": "7ad9db9dd2bb49738d8003e8aa4d22f9b93ba689",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_range_filter_module.c"
    }
  ]
}