@SD0001 suggested in chat that adding cache control via a maxage parameter would improve the usefulness of the proxy. He also noted that URLs including a full git hash should be immutable and thus eligible for automatic far future expiry and the 'immutable' directive.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
bd808 opened https://gitlab.wikimedia.org/toolforge-repos/gitlab-content/-/merge_requests/9
Add maxage Cache-Control support
Comment Actions
bd808 merged https://gitlab.wikimedia.org/toolforge-repos/gitlab-content/-/merge_requests/9
Add maxage Cache-Control support
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2025-05-21T21:29:23Z] <wmbot~bd808@tools-bastion-12> Built new image from 875a9ae2 (T393928)
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2025-05-21T21:30:27Z] <wmbot~bd808@tools-bastion-12> Restart to pick up new image (T393928)
Comment Actions
bd808 opened https://gitlab.wikimedia.org/toolforge-repos/gitlab-content/-/merge_requests/12
Automatically add 'immutable' Cache-Control header to permalinks
Comment Actions
bd808 merged https://gitlab.wikimedia.org/toolforge-repos/gitlab-content/-/merge_requests/12
Automatically add 'immutable' Cache-Control header to permalinks
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2025-07-20T17:58:27Z] <wmbot~bd808@tools-bastion-12> Built new image from 449e522e (T397571, T393928)
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2025-07-20T17:59:25Z] <wmbot~bd808@tools-bastion-12> Restarted to deploy new image from 449e522e (T397571, T393928)