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
We are facing an issue with Firefox where we want to open a Websocket with cookie authorization from a Domain A inside a Domain B. The team from Mozilla is saying that we would have to request Storage access in order to get access to the cookies.
This is super frustrating, as Websockets are pretty much only backend calls, and we actually do have the same Cookies in Domain A and Domain B. However, since the WebSocket is opening cross-origin, the cookies from neither domain are being passed in, and we can't even set custom headers in the request manually as Javascript's API doesn't support that.
Not sure what's the best way of handling this is, but getting the user to interact with an IFrame just for us to open a websocket in the background seems a bit overkill. Please find the Bugzilla tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1800799#c0
The text was updated successfully, but these errors were encountered:
That is what you'll have to do, including in Safari and at some point Chrome.
I suppose we can duplicate this into #107 as it's essentially the same request. (Though whether that feature will be added to the platform is as-of-yet unclear.)
We are facing an issue with Firefox where we want to open a Websocket with cookie authorization from a Domain A inside a Domain B. The team from Mozilla is saying that we would have to request Storage access in order to get access to the cookies.
This is super frustrating, as Websockets are pretty much only backend calls, and we actually do have the same Cookies in Domain A and Domain B. However, since the WebSocket is opening cross-origin, the cookies from neither domain are being passed in, and we can't even set custom headers in the request manually as Javascript's API doesn't support that.
Not sure what's the best way of handling this is, but getting the user to interact with an IFrame just for us to open a websocket in the background seems a bit overkill. Please find the Bugzilla tracker here: https://bugzilla.mozilla.org/show_bug.cgi?id=1800799#c0
The text was updated successfully, but these errors were encountered: