You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @Cervenka, do you have a use case in which you need to set it to include? I agree that it can be useful, but would like to know the use case before we move forward
In my case I'm sending requests to a different subdomain (app.domain.com --> legacy-api.domain.com) - so cross origin.
legacy-api.domain.com's responds with the correct CORS headers.
I need the request to include the cookies that are shared across *.domain.com.
With the option set to same-origin the cookies are not included - similar to XHR calls with withCredentials set to false.
It may be useful to be able to set the option
credentials
toinclude
.At the moment it is hardcoded to
same-origin
.https://github.com/rails/request.js/blob/main/src/fetch_request.js#L59
https://developer.mozilla.org/en-US/docs/Web/API/fetch#parameters
Thank you
The text was updated successfully, but these errors were encountered: