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

TLS support for non-blocking client #429

Closed
TechnoPorg opened this issue Jun 13, 2024 · 1 comment
Closed

TLS support for non-blocking client #429

TechnoPorg opened this issue Jun 13, 2024 · 1 comment
Labels

Comments

@TechnoPorg
Copy link

I am investigating making wss:// connections using tungstenite, for the sake of lemunozm/message-io#102.
Based on that issue, it seems that this crate does not support client-side TLS when using the tungstenite::client function to connect to a server.
It seems as though the blocking/non-blocking websocket connections should have feature parity, but since this currently isn't working, is there any workaround?

@daniel-abramov
Copy link
Member

TLS does not depend on the mode (blocking/non-blocking) of a socket.

client() function has never had any additional (TLS or other) logic. It only deals with the WebSocket connection.

client_tls() is the TLS counterpart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants