Automatic Decompression for GZIP and DEFLATE Content-Encoding in REST Connector
Currently, when using the REST connector, if a stream is gzip or deflate compressed, the data received is successful with a StatusCode of 200, but the body content is garbled due to the Content-Encoding being gzip'd at the source. This requires additional manual effort in transforming the data to be usable.
2
votes
![](https://secure.gravatar.com/avatar/c929c50815ebd083f54d4f7728cc5727?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)