Re: [whatwg/xhr] Where in the spec is the content-type header filtered out on 301/302/303 redirects? (#192)

Hmm. They do sound the same (or at least this seems to be a Fetch issue rather then XHR issue), but maybe there's still a detail that hasn't yet been considered.

In both of the tests I mention above, they end up being 301 redirects that drop from a POST to a GET, so both of them *should* lose their bodies and content-types... but the CORS-related one expects the safelisted content-type header to not be stripped away. And Chrome and Firefox are passing both tests, so I'm not sure why there isn't a conflict between these tests. That's why I think that it matters if the header was explicitly declared, which I don't see being considered in that Fetch issue.

-- 
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/xhr/issues/192#issuecomment-367008793