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?
1 Reply
potentially we changed somethiing as well which broke it — but caching headers, etc from the origin are fairly standard stuff...
hmm ok — if there's a cache miss then the response is compressed
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
https://community.cloudflare.com/t/return-compressed-response-from-worker/154117/3 🤔
will pick this up tomorrow
any tips in the meantime would be appreciated
If matters too the origins response is uncompressed atm
hmm apparently you have to return
content-encoding explicitly — but only gzip is supported for this atm and not brotli and zstd