@ryantownsend @PatMeenan @programmingart
Several do, yes. Here's a link to a place that pays my bills, lol. Regardless, one can safely assume that if Fastly supports zstd at various levels of the caching architecture, then partner CDNs do as well (for multiple reasons, only some of which are technical in nature).
Something to consider, when CDN marketing says "We support $thing", it's not just one layer of the data transit or data cached which is in play... data cached on persistent block storage, data compressed in volatile cache, data compression between cluster nodes, between customer origin and CDN ingress, during metadata log analysis and streaming metrics provided to the customer, and eventually data compression between the edge itself and the user's browser.
Does the QUIC handshake require compression to be fast?
QUIC promises a built-in, low-latency handshake. But can it achieve its promise alone? Letβs look at the value of handshake compression in helping QUIC achieve fast startup performance.
(www.fastly.com)