How Content-Encoding HTTP header is used and interacts with 10MB message size limit

[James_wang]

Hi Team，

As we known, By default To prevent memory issues in Edge, message payload size on the Router and Message Processor is restricted to 10MB. Exceeding those sizes results in a protocol.http.TooBigBody error( https://docs.apigee.com/private-cloud/v4.18.01/set-message-size-limit-router-or-message-processor ).

also, Apigee Edge takes care of all compression automatically. by default it will use the compression requested by the client.(https://www.googlecloudcommunity.com/gc/Apigee/Does-Apigee-support-compression-de-compression-with-G... ).

then, I have some question need your help.

• Are these limits checked before or after encoding of content? (e.g. gzip)?
• If backend provides an uncompressed body and client supports compression, does API Gateway compress the body in-flight? If so, is the 10MB limit enforced on the compressed or un-compressed body?
• If backend service provides a compressed body and appropriate Content-Encoding header, does API Gateway enforce the 10MB limit on the compressed or un-compressed body?

Any more details like relevant reference documents would be great. Thank you.