Skip to content

Restore conditional Cache-Control header - #1403

Merged
victorlin merged 1 commit into
masterfrom
victorlin/cache
Oct 26, 2026
Merged

victorlin merged 1 commit into
masterfrom
victorlin/cache

Conversation

@victorlin

Copy link
Copy Markdown
Member

#1402 wrongly assumed that this setting is the baseline that is overridden by other handlers. It turns out that Next.js and expressStaticGzip (used for Auspice assets) only set their defaults when Cache-Control has not already been set.

Ignore the claim in the previous commit message. Two wrongs make a right?

(Sorry for the PR spam. Cache control headers only apply in production and I've been testing on the canary site out of convenience.)

Checklist

"Clarify default Cache-Control header" (c39ec5a) wrongly assumed that
this setting is the baseline that is overridden by other handlers. It
turns out that Next.js and `expressStaticGzip` (used for Auspice assets)
only set their defaults when Cache-Control has not already been set.

Ignore the claim in the previous commit message. Two wrongs make a
right?
@victorlin victorlin self-assigned this Oct 26, 2026
@victorlin victorlin mentioned this pull request Oct 26, 2026
2 tasks done
@victorlin
victorlin merged commit 0913328 into master Oct 26, 2026
6 checks passed
@victorlin
victorlin deleted the victorlin/cache branch October 26, 2026 20:39
@victorlin victorlin mentioned this pull request Oct 27, 2026
1 of 2 tasks
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