This is really neat. There&#x27;s, I don&#x27;t know if it&#x27;s a niggle or a bug or an interface issue, but well, let&#x27;s call it a usability bug.<p>If your copy to curl request in chrome accepts gzip and&#x2F;or deflate, then your tool will add an &quot;Accept-Encoding&quot; Header. So far so good.<p>In go 1.5.1 at least, from my cursory testing, the runtime will not auto-decompress a bytestream if you&#x27;ve manually specified an accepted encoding.<p>On the other hand, if you leave it off, it will offer gzip to a server and auto uncompress on receipt.<p>I&#x27;m still not sure this is a bug, but I definitely commented out my accept encoding line in my sample code because I don&#x27;t want to manually decompress every response.<p>At any rate, thank you for making this; I&#x27;m using it with a slack integration right now.