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

Actually I may propose some custom implementation which will involve same work as proposed by the issue starter. So, with the header the work should be done both on server (to send okay, you may redirect header) and on client as well (client would have to check opaque/not, compose new url and make a new fetch).

#### custom redirect

Accepted content-type is JSON and a plaintext value (not "secured" by the spec yet) is a redirect URL. Other results are considered error. I've made some test to test it: 

http://raw.githack.com/determin1st/httpFetch/master/test-8/index.html

#### manual redirect wasted

@annevk if you keep on blocking my messages i would have to search w3c contacts.
Because spec doesn't move anywhere (it moves nowhere) and it may be considered as private agreements if you continue.



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