Skip to content

fix(llms): send a public max-age so shared caches can store llms.txt - #75

Merged
mhenrixon merged 1 commit into
mainfrom
fix/llms-cache-max-age
Aug 27, 2026
Merged

fix(llms): send a public max-age so shared caches can store llms.txt#75
mhenrixon merged 1 commit into
mainfrom
fix/llms-cache-max-age

Conversation

@mhenrixon

@mhenrixon mhenrixon commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

Live check on glyphs.zoolutions.llc/llms.txt showed Cache-Control: public with no max-age, so the newly enabled proxy.cache never stored it. expires_in 300, public: true before stale? fixes that; the etag revalidation is unchanged.

https://claude.ai/code/session_01SdEc37DFCkYzwpQpadu9My


Summary by cubic

Fixes /llms.txt caching so shared caches like dash-proxy and CDNs can store it. Previously Cache-Control: public had no max-age, so RFC 9111-compliant caches skipped the response. Added expires_in 300, public: true before the etag stale check; revalidation still works.

Written for commit 28b771b. Summary will update on new commits.

Review in cubic

`public` alone is not storable under RFC 9111 — the dash-proxy response
cache skipped /llms.txt for lack of a freshness lifetime. 300s matches the
proxy.cache.max_ttl docs-kit scaffolds; the etag still revalidates.

Claude-Session: https://claude.ai/code/session_01SdEc37DFCkYzwpQpadu9My
@mhenrixon
mhenrixon merged commit 10068e0 into main Aug 27, 2026
6 checks passed
@mhenrixon
mhenrixon deleted the fix/llms-cache-max-age branch August 27, 2026 15:47
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.

1 participant