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