- From: seven <notifications@github.com>
- Date: Sun, 19 Mar 2017 09:27:42 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 19 March 2017 16:28:13 UTC
**Chrome version**: 57.0.2987 Actually, in older Chrome version I also have this problem. I added `Authorization` on Request Header with my access token, ``` { headers: { 'Authorization': 'Bearer ' + accesstoken } } ``` I always get `Access-Control-Allow-Headers:authorization` in Chrome Besides, My fetch is always Request Method:**OPTIONS** (not display get), then `Status Code` is 200 OK in Chrome But if I run the same fetch code in Firefox (ver 52.0.1 ), everything works great. I can add `Authorization` on Request Header correctly. It will display `Authorization: Bearer accesstoken` on Request header. The server side already processed CORS for my request header.. This is a Chrome bug or my code fault? How should I do to make `Authorization` on Request Header correctly? -- 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/509
Received on Sunday, 19 March 2017 16:28:13 UTC