- Shipped
- September 28, 2026 at 9:22 PM UTC
- Author
- Kamo
- Commit
- 3462c8a
After its stale service worker was replaced, the owner's browser went on sending https://kamouniverse.com/ to www.kamocrm.com without asking any server. From 2026-09-23 to 09-27 a Traefik redirectRegex had 301'd kamouniverse.com to www.kamocrm.com with no Cache-Control, and Chrome keeps a 301/308 like that forever. This service's own 308s had the same flaw, so the next change of an apex target would have stranded browsers the same way. Every redirect now goes out with Cache-Control: public, max-age=3600. Browsers re-ask within the hour and a changed target reaches them. It is still a 308, so search engines keep treating it as permanent. Verified against a local production build: every redirect (bare apex, http upgrade of an alias, http upgrade of a subdomain) carries the header with path and query kept. /sw.js still answers 200 no-store, and /api/health returns 200.