- Shipped
- September 28, 2026 at 9:23 PM UTC
- Author
- Kamo
- Commit
- 8fc0ad9
From 2026-09-23 to 09-27 the kamouniverse-to-kamocrm redirectRegex 301'd kamouniverse.com to www.kamocrm.com. Traefik sends such a redirect with no Cache-Control, and Chrome keeps a 301/308 like that forever. So after the apex was repointed at www.kamouniverse.com, the owner's browser still went to www.kamocrm.com without sending a single request. The same trap was set for the four audience domains (kamofamily.org, kamobusiness.com, kamopersonal.com, kamocommunity.org). They forward to www.kamouniverse.com only until their own sites launch, and every browser that saw the forward would have stayed forwarded. dev.kamouniverse.com is in the same position. A new shared headers middleware, redirect-cache-one-hour (Cache-Control: public, max-age=3600), now runs first on those four routes. It wraps the redirect middleware, so the header lands on the 301/308 that middleware writes. Browsers re-ask within the hour; search engines still see a permanent redirect. Checked against live before pushing: `kubectl diff` of every file the traefik step applies shows only this change plus the pre-existing meet-route label flip (app: kamomeet vs kamo-meet; Traefik has no label selector). traefik/deployment.yaml is clean, so no Traefik rollout. The server dry-run accepts all five objects.