From ab88303dc159162ed15352855587f47c8def0352 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Sat, 31 Oct 2026 14:54:49 -0700 Subject: Say cgit pages carry no expiry, not no headers Behind an auth filter every page carries Cache-Control: private and the login page no-store, so only the missing expiry holds on every site. --- custom/servers/apache.conf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'custom/servers/apache.conf') diff --git a/custom/servers/apache.conf b/custom/servers/apache.conf index 6c85ee3..3d65d5e 100644 --- a/custom/servers/apache.conf +++ b/custom/servers/apache.conf @@ -136,8 +136,8 @@ AddType text/plain .txt Require all granted # These assets rarely change, so let browsers cache them. Keep the - # caching scoped to this directory. Ordinary cgit pages carry no caching - # headers, so a server-wide ExpiresDefault would stamp freshness onto + # caching scoped to this directory. Ordinary cgit pages carry no expiry + # time, so a server-wide ExpiresDefault would stamp freshness onto # them, fight the no-store cgit puts on the login page, and could let # one visitor's page be served to another from a shared cache. -- cgit