Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request Access for WebSockets? #140

Closed
OskarEichler opened this issue Nov 24, 2022 · 1 comment
Closed

Request Access for WebSockets? #140

OskarEichler opened this issue Nov 24, 2022 · 1 comment

Comments

@OskarEichler
Copy link

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

@annevk
Copy link
Collaborator

annevk commented Nov 24, 2022

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.)

@annevk annevk closed this as not planned Won't fix, can't repro, duplicate, stale Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants