I noticed an issue with Chrome 42+ where cookies would not be sent when using the request API provided by the http state source. After some investigation, I found out that Chrome's implementation of fetch does send any cookies by default (https://github.com/github/fetch/issues/121). So, in order to make Chrome's behavior consistent, the credentials options must be set to "same-origin".
Let me know if you think that this could cause some undesirable effects, but I think this change will only align the behaviors of the fetch polyfill and Chrome's native fetch.
I noticed an issue with Chrome 42+ where cookies would not be sent when using the request API provided by the http state source. After some investigation, I found out that Chrome's implementation of fetch does send any cookies by default (https://github.com/github/fetch/issues/121). So, in order to make Chrome's behavior consistent, the credentials options must be set to "same-origin".
Let me know if you think that this could cause some undesirable effects, but I think this change will only align the behaviors of the fetch polyfill and Chrome's native fetch.