zstd broken

I have a zone with zstd enabled for the last month or so and just noticed that it's not working anymore. And it's not just that zstd compression isn't happening but all compression is somehow disabled.

Did something break here?

Kyle MathewsOP•12/3/24, 11:48 PM

potentially we changed somethiing as well which broke it — but caching headers, etc from the origin are fairly standard stuff...

Kyle MathewsOP•12/3/24, 11:56 PM

hmm ok — if there's a cache miss then the response is compressed

Kyle MathewsOP•12/3/24, 11:57 PM

I'm using a cloudflare worker to proxy the request to the origin — so when the cloudflare worker's fetch hits the cache, its returning uncompressed data

Kyle MathewsOP•12/3/24, 11:59 PM

https://community.cloudflare.com/t/return-compressed-response-from-worker/154117/3

Kyle MathewsOP•12/3/24, 11:59 PM

will pick this up tomorrow

Kyle MathewsOP•12/3/24, 11:59 PM

any tips in the meantime would be appreciated

Kyle MathewsOP•12/4/24, 12:23 AM

If matters too the origins response is uncompressed atm

Kyle MathewsOP•12/4/24, 2:28 AM

hmm apparently you have to return content-encodingcontent-encoding explicitly — but only gzipgzip is supported for this atm and not brotli and zstd

zstd broken

Similar Threads

Similar Threads

Similar Threads