HTTP: invalid gzip response when compression is enabled
The client tries to unpack the data and reports an error despite status 200.
How to identify the source of the problem
Compare Content-Encoding with body bytes and see if CDN does not compress compressed data anymore.
Save method, status, headers and anonymized body requests and answers.
Repair steps
Remove double encoding or correct headers according to the actual content sent.
How to Test Solution
The answer can be unpacked and parsed in the browser and using curl.
Security and restrictions
Do not disable authorization or validation of webhook signature for status 200. Wash the tokens in the logs.