Re: [whatwg/fetch] Drop developer-controlled Authorization header on cross-origin redirects (#944)

> (If you use other headers to carry credentials you are out of luck.)

I'm sure there is a good reason for this, so apologies if this has been discussed to death; is there a thread that discusses the motivation of sending custom-set headers by default on redirects to cross-origin domains? The `Authorization` header seems an obvious candidate for not being sent cross-origin. But, what if folks are doing stuff like `MyApp-API-Token: .....`? Intentional redirect to third-parties are not super rare, and it seems surprising/a possible foot-gun to relay all custom headers to another origin without the caller opting into that behavior. 

-- 
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/944#issuecomment-537059998