We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If available, websocket connections should be redirected through the browser extension, just like HTTP ones.
This has been already suggested in #2194 but the issue was closed by the author as completed, even though it's not completed.
Because developing websockets is almost impossible else, since HTTPS pages can only connect to wss sockets, and in development TLS is usually skipped
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
Summary
If available, websocket connections should be redirected through the browser extension, just like HTTP ones.
This has been already suggested in #2194 but the issue was closed by the author as completed, even though it's not completed.
Why should this be worked on?
Because developing websockets is almost impossible else, since HTTPS pages can only connect to wss sockets, and in development TLS is usually skipped
The text was updated successfully, but these errors were encountered: