We have a requirement to support compression/de-compression on an Apigee bundle.
I found a link on Apigee specifically below help page:
http://apigee.com/docs/api-services/reference/endpoint-properties-reference
I had a couple of queries around this:
1) Does it actually compress/decompress when I send traffic to Target endpoint? Or does it support the headers related to compression/decompression only?
2) In the scenario, where I get gzip/deflate compressed data, is it possible for my proxy to uncompress this data before sending it to backend target?
3) In the same scenario as above, Can I send the compressed data as is to target endpoint
Any more details like how to validate and test this would be great.
Solved! Go to Solution.
Hi,
Apigee Edge takes care of all compression automatically. As the document you linked to says, by default it will use the compression requested by the client, but you can change that using the target endpoint configuration.
The message is uncompressed when executing the request and response flows -- you never will see compressed data, and this all happens automatically.
You can test this using a test target like httpbin.org. The endpoint http://httpbin.org/gzip returns gzipped data, and you can see what kind of compression was sent to it.
Mike