Use immutable only with a stable resource version

The useful distinctions

• immutable is a Cache-Control response extension.
• It indicates that a response will not change while fresh.
• It does not create an infinite freshness lifetime.

Tie the promise to publication behavior

A publisher can make a resource easier to reuse by giving each revision a distinct URL. In the synthetic path, v12 is a release label selected by the publisher. The operational promise is that this path continues to identify those same bytes during the declared freshness interval. If a new initialization resource is needed, publishing it at a new path keeps that promise understandable. Merely inserting a version-looking word in a path does not enforce the behavior.

Review replacement and rollback together

Before adopting this pattern, write down how a corrected file, a rollback, and a mistaken upload would receive their own identifiers. That review exposes cases where an operator might otherwise overwrite a supposedly stable object. The example's one-hour allowance is intentionally modest so the relationship is visible without recommending a production lifetime. The immutable field does not validate a media container, guarantee decoder support, or establish a connection's security. It is a statement about reuse of this response while it remains fresh. A changing manifest and the stable objects it references can reasonably require different policies. A versioned path also makes the worksheet easier to audit: record the path and its publication revision together, then flag any later replacement under that same version label for a separate publishing review.

Worked example · synthetic

The invented path expresses a publisher's version convention. The meaningful review is whether that resource is actually kept stable during its 3600-second freshness allowance.

Synthetic text example; no network operation has been performed.

HTTP/MIME line endings are CRLF. Request URL context, where labelled, is commentary rather than a wire field. No message was transmitted.

HTTP/1.1 200 OK
Date: Sun, 08 Nov 2026 08:00:00 GMT
Content-Location: /samples/v12/init.mp4
Cache-Control: max-age=3600, immutable
Content-Length: 0

Check the interpretation

• Confirm versioned resources are not overwritten while fresh.
• Define correction and rollback paths.
• Do not describe immutable as permanent storage.