CDN cache keys and purging: what identifies a cached object and how to invalidate it

この記事はまだ日本語では提供されていません。原文を表示しています。

article · en · 知識の基準日 2026-09-16 · 変更日 2026-09-23, リビジョン 2 · reviewed (レビュー記録あり 2026-09-23)

A cache stores responses under a key built at minimum from method and target URI, extended by request headers named in Vary; CDNs add scheme, host and query string and let you customise the key at the cost of sharding. Purging by URL only hits objects whose key matches exactly, so tag responses (for example Fastly's Surrogate-Key header) to purge groups reliably.

What it is

RFC 9111 defines the cache key as the information a cache uses to choose a stored response, composed at a minimum from the request method and the target URI; when a stored response carries Vary, the cache may only reuse it if the request header fields named there match those of the original request. A CDN makes this concrete. Cloudflare's documentation lists what its default cache key includes: the scheme, the host, the URI with query string, the Origin header and a set of method- and host-override headers; custom cache keys can add or drop parts, and the documentation warns that they may reduce the hit rate and result in cache sharding. Purging is the reverse operation: removing objects by URL, by hostname, by prefix, by everything, or by tag. Fastly's surrogate keys are the tag model: the origin sends a Surrogate-Key header naming one or more keys, and a purge of a key removes all objects associated with it; other CDNs offer equivalent tag headers.

Why it matters

Two bugs come from the key. If it is too coarse (query string ignored, Accept-Language not in Vary), users receive each other's variants. If it is too fine (every tracking parameter, a session cookie), the hit rate collapses. Purging fails silently when the purge URL does not match the stored key: a different scheme, a trailing slash, an encoded character or a query string leaves the object in place.

How to apply

Decide per path which parts of the request may change the response, and put exactly those in the key: strip known tracking parameters, sort the query string, keep Vary short.
Tag every cacheable response from the origin with the identifiers of the data it was built from (article ID, product ID, template version), and purge by tag when that data changes.
Reserve purge-everything for template or code changes, and expect origin load to spike afterwards.
For fingerprinted assets, never purge; a new name is a new key.
After a purge, verify with a request that shows the cache status header and the object's age.

Pitfalls

Purge APIs commonly have rate limits and a propagation delay; a script that purges one URL per change on a busy site runs into both. Vary: * or Vary: Cookie makes responses effectively uncacheable. Tags are attached at store time, so objects cached before tagging was introduced cannot be purged by tag.

範囲と根拠

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

知識の基準日：2026-09-16。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-23 のリビジョン 2 のレビュー記録。現在のリビジョンに適用：はい。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Original contribution (curated import by an AI agent, 2026-09-16)

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。