Trusted Server serves many content types through one edge hostname; HTML, JS bundles, creatives/images, static assets, RTB/JSON — each with a different optimal caching posture, all driven by the cache directives the origin returns (Cache-Control, Surrogate-Control, Surrogate-Key, Vary, ETag). Today TS mostly passes these through untouched and exposes no cache diagnostics, so a publisher developer can't tell whether each content type is cached correctly. The result is silent over-caching (personalized/consent-sensitive HTML served stale or shared across users) and under-caching (immutable assets re-fetched from origin every request).
This epic delivers ts dev audit headers, a CLI command that audits origin response cache directives grouped by content type and returns a per-type pass/warn/fail verdict naming the responsible header and recommending the correct value; so misconfigured caching is caught before it hurts hit ratio or leaks personalized content.
Out of scope: auto-fixing headers, request-side cache-key/hit-ratio analysis, and the ts dev proxy tool.
Note: ts dev audit headers slots into the same ts dev CLI group
Trusted Server serves many content types through one edge hostname; HTML, JS bundles, creatives/images, static assets, RTB/JSON — each with a different optimal caching posture, all driven by the cache directives the origin returns (Cache-Control, Surrogate-Control, Surrogate-Key, Vary, ETag). Today TS mostly passes these through untouched and exposes no cache diagnostics, so a publisher developer can't tell whether each content type is cached correctly. The result is silent over-caching (personalized/consent-sensitive HTML served stale or shared across users) and under-caching (immutable assets re-fetched from origin every request).
This epic delivers ts dev audit headers, a CLI command that audits origin response cache directives grouped by content type and returns a per-type pass/warn/fail verdict naming the responsible header and recommending the correct value; so misconfigured caching is caught before it hurts hit ratio or leaks personalized content.
Out of scope: auto-fixing headers, request-side cache-key/hit-ratio analysis, and the ts dev proxy tool.
Note:
ts dev audit headersslots into the same ts dev CLI group