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
AdminJeffery Maynard
(Product Support Consultant, Novacura)
shared this idea