)]}'
{
  "commit": "ef76b584da7329ffee1e30286c0bf76b255ad3cc",
  "tree": "08b83bc0ece3aa14c15b99eec844c75bd70f8781",
  "parents": [
    "6f7a1824b5e38194146dd8516c48a4a7663a0d14"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 13:53:50 2012 +0000"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Sun Feb 05 13:53:50 2012 +0000"
  },
  "message": "Merge of r4372, r4373, r4374:\n\nSCGI fixes:\n\n*) Fixed incorrect use of r-\u003ehttp_version in scgi module.\n\n   The r-\u003ehttp_version is a version of client\u0027s request, and modules\n   must not set it unless they are really willing to downgrade protocol\n   version used for a response (i.e. to HTTP/0.9 if no response headers\n   are available).  In neither case r-\u003ehttp_version may be upgraded.\n\n   The former code downgraded response from HTTP/1.1 to HTTP/1.0 for no\n   reason, causing various problems (see ticket #66).  It was also\n   possible that HTTP/0.9 requests were upgraded to HTTP/1.0.\n\n*) Removed duplicate function declaration.\n\n*) Removed error if there is no Status header.\n\n   The SCGI specification doesn\u0027t specify format of the response, and\n   assuming CGI specs should be used there is no reason to complain.\n   RFC 3875 explicitly states that \"A Status header field is optional,\n   and status 200 \u0027OK\u0027 is assumed if it is omitted\".\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "168f497ce0c2607a28bc4c84a84d30e55db32ff0",
      "old_mode": 33188,
      "old_path": "src/http/modules/ngx_http_scgi_module.c",
      "new_id": "e6c3afaed06fc69ad433f7b98e1f3576f5983826",
      "new_mode": 33188,
      "new_path": "src/http/modules/ngx_http_scgi_module.c"
    }
  ]
}