{"push_id":573727247,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ae9b5c9e3cab80c2701f53f192ad2975e3664ea6","before":"a67afa16197a7f9936d8e720a7359a08931b2a6a","commits":[{"sha":"ae9b5c9e3cab80c2701f53f192ad2975e3664ea6","author":{"email":"93f299ce2d5df8f33686d44277fd40d3022bdd84@gmail.com","name":"James Abley"},"message":"Clients MUST support gzip\n\nFrom the spec – http://www.chromium.org/spdy/spdy-protocol/spdy-protocol-draft3-1\n\n“User-agents MUST support gzip compression. Regardless of the\nAccept-Encoding sent by the user-agent, the server may always send\ncontent encoded with gzip or deflate encoding.”\n\nThis change adds transparent decompression of gripped content.\n\nI found this when I modified client code to use SPDY to talk to an\norigin server. The origin is using nginx. I was getting errors when\ntrying to unmarshall JSON:\n\n```\ninvalid character '\\\\x1f' looking for beginning of value\n```\n\nEnabling debug logging, I saw the request:\n\n```\nHeader:               map[Url:[/public/dashboards?slug=carers-allowance] Version:[HTTP/1.1] Host:[example.gov.uk] Scheme:[https] Accept:[application/json] User-Agent:[Performance-Platform-Client/1.0] Accept-Encoding:[gzip] Method:[GET]]\n```\n\nand a response:\n\n```\nmap[Status:[200] Content-Type:[application/json] Via:[1.1 varnish] Date:[Thu, 12 Feb 2015 19:52:58 GMT] Cache-Control:[max-age=300] Access-Control-Allow-Origin:[*] X-Frame-Options:[SAMEORIGIN] X-Varnish:[1873677853 1873677852] Age:[0] X-Cache:[HIT] Content-Encoding:[gzip] Version:[HTTP/1.1] Server:[nginx] Alternate-Protocol:[443:npn-spdy/2 443:npn-spdy/2] Strict-Transport-Security:[max-age=2628000]]\nData:                 [1f 8b 08 00 00 00 00 00 00 ... 05 af e6 9f 47 2a 3c 00 00]\n```\n\nThis shows that the response is coming back compressed, even though the\nclient didn’t ask for that.","distinct":true,"url":"https://api.github.com/repos/jabley/spdy/commits/ae9b5c9e3cab80c2701f53f192ad2975e3664ea6"}]}