)]}'
{
  "commit": "a547f4ac15a489be896edb353a71f2dc85af1265",
  "tree": "71d6ab120080e9946669b5cf1bd759ee36733feb",
  "parents": [
    "108e4d94e4585085f3244f50905d772d089bcb70"
  ],
  "author": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Mon Apr 07 19:27:56 2014 +0400"
  },
  "committer": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Mon Apr 07 19:27:56 2014 +0400"
  },
  "message": "SPDY: consistently handle control frames with unknown type.\n\nThe SPDY draft 2 specification requires that if an endpoint receives a\ncontrol frame for a type it does not recognize, it must ignore the frame.\nBut the 3 and 3.1 drafts don\u0027t seem to declare any behavior for such case.\nThen sticking with the previous draft in this matter looks to be right.\n\nBut previously, only 8 least significant bits of the type field were\nparsed while the rest of 16 bits of the field were checked against zero.\nThough there are no known frame types bigger than 255, this resulted in\ninconsistency in handling of such frames: they were not recognized as\nvalid frames at all, and the connection was closed.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9e4ac3476775a2513b8fc2b3779cbcdc2fe95f86",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_spdy.c",
      "new_id": "33f0f03ac338aa878e0baac67c96924924bf1015",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_spdy.c"
    }
  ]
}