Re: [w3c/ServiceWorker] support efficient offline redirects (#1457)

Have the sites indicated what problems they're running into with HTTP 301 redirects?  (Aggressive HTTP cache eviction?  It's not actually one URL but instead a whole family of URLs?  Concern about ability to later re-sell the domain and so they don't actually want a truly permanent redirect?  Actually want the vanity domain to be the domain the user sees but don't want to actually serve off the domain?)

Because one advantage of something like a 301 redirect is that it can be propagated back towards the input method, for example Firefox's awesomebar, so that URLs can be updated and the redirect chain doesn't need to be followed on every visit.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1457#issuecomment-521080793