We just shipped support for the ugliest part of HTTP: Vary

Cloudflare has introduced Vary support in Cache Rules across all plans to help sites cache multiple valid representations of a URL without excessive cache fragmentation. The HTTP Vary header tells caches which request headers may influence a response, such as Accept, Accept-Language, or Accept-Encoding, but raw header differences can create many separate cache entries even when an origin produces identical content. Cache Rules lets customers decide how Cloudflare handles each Vary field through normalization, which groups equivalent negotiation preferences; passthrough, which preserves exact header values for controlled variations; and bypass, which avoids caching for personalized or unpredictable fields such as cookies or user agents. Cloudflare recommends normalization for common content negotiation, while stressing that origins must consistently return correct Vary headers, including on error and fallback responses, to prevent incorrect cache reuse. The feature can be configured through the Cloudflare dashboard, Rulesets API, or Terraform, and is intended to provide a response-driven alternative to custom cache keys, which apply request dimensions to every covered response regardless of whether the origin varies on them.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.