)]}'
{
  "commit": "db8a0c8bf1d07936691107a4ea1626112541250c",
  "tree": "a6e14b600e72500cd5389345a8915e237dc4b44a",
  "parents": [
    "3be925b6e3c79a2030beaceb7feb0253e0ef17b5"
  ],
  "author": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Aug 15 19:16:09 2013 +0400"
  },
  "committer": {
    "name": "Valentin Bartenev",
    "email": "vbart@nginx.com",
    "time": "Thu Aug 15 19:16:09 2013 +0400"
  },
  "message": "SPDY: do not reject headers with empty value (ticket #396).\n\nA quote from SPDY draft 2 specification: \"The length of each name and\nvalue must be greater than zero.  A receiver of a zero-length name or\nvalue must send a RST_STREAM with code PROTOCOL error.\"\n\nBut it appears that Chrome browser allows sending requests over SPDY/2\nconnection using JavaScript that contain headers with empty values.\n\nFor better compatibility across SPDY clients and to be compliant with\nHTTP, such headers are no longer rejected.\n\nAlso, it is worth noting that in SPDY draft 3 the statement has been\nchanged so that it permits empty values for headers.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d72bc3f7c1213af60ff50b43a54346d896e7218e",
      "old_mode": 33188,
      "old_path": "src/http/ngx_http_spdy.c",
      "new_id": "8522c6d0a68036e34c349e195feccd2a11625e4d",
      "new_mode": 33188,
      "new_path": "src/http/ngx_http_spdy.c"
    }
  ]
}