Does cloudflare cdn support zstd
#Does cloudflare cdn support zstd
quartz rain
wet tulip
Does cloudflare cdn support zstd
Only gzip and brotli right now, and brolti to origin was rolling out earlier this year, I think it's all finished now though:
https://developers.cloudflare.com/speed/optimization/content/brotli/content-compression/
quartz rain
thx
wet tulip
zstd isn't supported by browsers really: https://caniuse.com/zstd
would need that first
quartz rain
its in chrome
wet tulip
just in chrome yea, and 123 just made it to stable right? Got a while to go
caniuse estimates 0.02% of users currently support it lol
there's a forum suggestion if you want to upvote it: https://community.cloudflare.com/t/add-support-for-zstd-as-a-content-encoding/604123
CF in their brotli to origin blog as well
Looking forward, we are closely following trends and new compression algorithms such as zstd as a possible next-generation compression algorithm.
https://blog.cloudflare.com/this-is-brotli-from-origin
So maybe eventually
opaque tree
Hey, sorry for visiting old thread but does cloudflare support zstd compression from origin servers or are brotli/gzip the only options?
I saw this release but wasn't able to understand if this is just for the users->cloudflare or cloudflare->origin?
#releases message
opaque tree
According to this page not yet: https://developers.cloudflare.com/speed/optimization/content/brotli/content-compression/
wet tulip
I saw this release but wasn't able to understand if this is just for the users->...
Just users->cloudflare
opaque tree
What would be the best place to ask support for this? zstd allows me to store so much more data in the origin server and it would save compute power (and environment 🌍 ) if I could just pass these files directly to cloudflare without decompressing them first.
I do understand it's probably still far away
wet tulip
I do understand it's probably still far away
it took 6 years from gzip being added at edge for it to be accepted from origins
so yea might be a bit lol. I think now fundamentally too zstd from edge is nginx/in front end code and the origin requesting code lives entirely in pingora/rust, so entirely different stacks, probably some of the reason for the delay
opaque tree
Thanks! That's great expectation management from you but I'm willing to wait 6 or more years 🙉