- From: h110m <notifications@github.com>
- Date: Mon, 01 Mar 2021 07:08:39 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 1 March 2021 15:08:51 UTC
I didn't really mean that I can set the cookie header myself in chrome. I just wanted to say that the cookies are sent with the fetch request in chrome as they should be because of `credentials: 'same-origin'`. I still can't set the cookie header myself in chrome. But at least it works with the credentials flag. Also when I don't include the credentials flag in chrome it sends the cookies with the request and this should happen since I read that it is set to 'same-origin' by default. But like I said in Firefox none of the values for the 'credentials' flag works and I don't know why. I mean like I said it would be nice if someone could test this so that I know that this is not specific because I am using fetch wrong or something. -- 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/1182#issuecomment-788020803
Received on Monday, 1 March 2021 15:08:51 UTC