)]}'
{
  "commit": "6f7a1824b5e38194146dd8516c48a4a7663a0d14",
  "tree": "40cd5a7d7e1bebc208870d27c7a9167f2cda8558",
  "parents": [
    "cb15836d9afc3a663c0811db3f47ed43010d7c7b"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 13:34:08 2012 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 13:34:08 2012 +0000"
  },
  "message": "Merge of r4339, r4340, r4341:\n\nCache fixes:\n\n*) Obsolete code removed.\n\n   The ngx_http_cache() and ngx_http_no_cache_set_slot() functions\n   were replaced in 0.8.46 and no longer used since then.\n\n*) Handling of cache files with long headers.\n\n   There are two possible situations which can lead to this: response\n   was cached with bigger proxy_buffer_size value (and nginx was\n   restared since then, i.e. shared memory zone content was lost), or\n   due to the race in the cache update code (see [1]) we\u0027ve end up\n   with fcn-\u003ebody_start from a different response stored in shared\n   memory zone.\n\n*) Only complain on long locked entries.\n\n   There have been multiple reports of cases where a real locked entry\n   was removed, resulting in a segmentation fault later in a worker\n   which locked the entry.  It looks like default inactive timeout isn\u0027t\n   enough in real life.\n\n   For now just ignore such locked entries, and move them to the top of\n   the inactive queue to allow processing of other entries.\n\n[1] http://mailman.nginx.org/pipermail/nginx-devel/2011-September/001287.html\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "efad6a3267970d0c6872bc3c8ca78cb67d183863",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_file_cache.c",
      "new_id": "a7c66736beeffcdc532651d4a1d95aed062e0998",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_file_cache.c"
    }
  ]
}