Problematic 301 redirects (no cache control)

Webflow wants to handle the naked domain redirect to www for us.
That’s nice.

Unfortunately webflow uses a 301 (permanent) redirect without any cache-control headers which means browser will cache this as long as possible and won’t check again.

This means that if we move to another site or have to revert our site (our previous site was hosted on naked domain with www redirecting to root) we cannot do this easily because anyone that saw the new site will have the permanent redirect cached.

Webflow should either add cache-control header on the 301 so that users check back once per hour or switch to 302.

…if they don’t then we are effectively stuck on www forever unless we want to try and tell the internet to force clear their browser caches. Hah.

Poorly thought out on webflows part. Something to be aware of if you care about things like this. You may want to maintain your own redirect to avoid this issue until webflow fixes it.