I was surprised to see that the C++ core interprets
"grpc-accept-encoding: deflate" like HTTP: it compresses messages using
zlib with deflate compression, rather than using raw deflate. Matching
HTTP semantics makes sense, of course, but this misnomer has
historically confused HTTP implementations too.
This detail didn't seem important enough to warrant inclusion in the
main protocol specification, so I've proposed an addition to
`docs/compression.md` to document the expected behavior. I'm happy to
move the addition around if you'd prefer it elsewhere.
Akshay Shah