AnsweredAssumed Answered

Gzip or not Gzip, that is the question

Question asked by PhBrand on Feb 19, 2019
Latest reply on Feb 22, 2019 by Charles_Lilienkamp

We have a use case where we need to reduce payloads. Using 9.3CR03 Gateway.

 

Netflow:   <External Partner> --> <DMZ API Gateway> ----> <LAN API Gateway>   ----> <Application>

 

We would like to transparently send back Application's gziped content-encoded parts without API gateway uncompressing/re-compressing it.

 

As far as I can see, API Gateway, when receiving a content-encoding/content-length header pair, automatically uncompress body.

 

Return template:

Size=${request.size}
Body=${request.parts.1.size}
Headers_req=${request.http.allheadervalues}

 

Result:

Size=394380
Body=394380
Headers_req=accept:*/*, accept-encoding:gzip, deflate, cache-control:no-cache, connection:keep-alive, content-encoding:gzip, content-length:40361, content-type:application/octet-stream, host:xxxxxxxxxxxxxxxxx, postman-token:e8e44510-629f-4f5f-bb5c-fa5f0954c061, user-agent:PostmanRuntime/7.6.0

 

So actual data sent it 40361 bytes, but gateway uncompress body and reveal original size of  394390 bytes.

 

Is it something doable ?

Outcomes