Skip to content

Add cache-header audit design spec for ts dev audit headers#930

Open
vasujain00 wants to merge 1 commit into
IABTechLab:mainfrom
vasujain00:spec/834-audit-headers
Open

Add cache-header audit design spec for ts dev audit headers#930
vasujain00 wants to merge 1 commit into
IABTechLab:mainfrom
vasujain00:spec/834-audit-headers

Conversation

@vasujain00

Copy link
Copy Markdown
Contributor

Technical spec for epic #834: origin cache-header audit with per-content-type cacheability diagnostics. Covers content-type taxonomy, cacheability rules for all five directives (Cache-Control, Surrogate-Control, Surrogate-Key, Vary, ETag), per-type verdict rollup, CLI integration into the ts dev group, and a 7-task implementation breakdown.

Closes #835

Summary

Changes

File Change

Closes

Closes #

Test plan

  • cargo test-fastly && cargo test-axum
  • cargo clippy-fastly && cargo clippy-axum
  • cargo fmt --all -- --check
  • JS tests: cd crates/trusted-server-js/lib && npx vitest run
  • JS format: cd crates/trusted-server-js/lib && npm run format
  • Docs format: cd docs && npm run format
  • WASM build: cargo build --package trusted-server-adapter-fastly --release --target wasm32-wasip1
  • Manual testing via fastly compute serve
  • Other:

Checklist

  • Changes follow CLAUDE.md conventions
  • No unwrap() in production code — use expect("should ...")
  • Uses tracing macros (not println!)
  • New code has tests
  • No secrets or credentials committed

Technical spec for epic IABTechLab#834: origin cache-header audit with
per-content-type cacheability diagnostics. Covers content-type
taxonomy, cacheability rules for all five directives (Cache-Control,
Surrogate-Control, Surrogate-Key, Vary, ETag), per-type verdict
rollup, CLI integration into the ts dev group, and a 7-task
implementation breakdown.

Closes IABTechLab#835
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create spec and plan to audit publsher origin headers

1 participant