Re: [whatwg/fetch] Header to opt out of opaque redirect (#601)

> All the workarounds are nasty. Maybe we can intoduce a new HTTP response header Location-Policy. We could expose the Location to javascript if it sets to some value.

This is what was proposed above... setting the redirect flag to manual.

The problem is that those in control of this spec have a fundamental issue with this approach.  To be honest, this issue is dead and buried - even if common sense prevails. 

The existing implementations of fetch in the wild are impossible to polyfill, nor detect when necessary to do so.  We cannot trust what the browser will do so we have to assume it won't be able to read the header and stop sending back 30x.

When standards bodies put their head in the sand, industry works around the problem, then we ignore the standards - to everyone's detriment.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/601#issuecomment-1055922815
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/601/1055922815@github.com>