LLL Cache-Control Builder / キャッシュヘッダー作成

How are public responses chosen? A mutable public route must return the same data regardless of the visitor. Select the versioned option only when the URL changes every time the file changes. Private modes do not accept shared-cache lifetimes.

What does comparison cover? It compares simple directives and unsigned durations from one response field. Directive order and name casing are ignored; missing, changed and extra directive names are listed. Quoted and duplicate directives need separate review. The tool does not simulate actual browser or CDN behavior, apply headers, fetch URLs, or purge previously stored copies.

What is the age range? Generated headers accept up to one year in whole seconds. A mutable public route with zero browser age uses public revalidation, with no separately specified shared age.

See RFC 9111 and RFC 8246 for HTTP cache and immutable response rules.

Requires an EmDash administrator with plugins:manage. The manifest requests no capabilities or network hosts. Inputs are processed in the sandbox without saving or external transmission. Paste only the Cache-Control response field. Accepting a preview does not configure caches or guarantee confidentiality. Report security issues to contact@lx3.cafe.

0.1.0

• Preview Cache-Control policies and compare them with observed response directives.

Install LLL Cache-Control Builder in EmDash 1.4 and open it as an administrator. Choose the response type for one route, and add freshness seconds if that choice allows it. Optionally paste one current Cache-Control response header, without other header lines. Select Preview policy. Use the resulting text to review or update your deployment configuration. Verify the resulting live response separately.