-
Notifications
You must be signed in to change notification settings - Fork 277
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
[BUG] Websocket over TLS in iroha_client doesn't work with rustls (default configuration) #4120
Comments
It appears to not be a bug, but a gotcha with using a re-exported sync version of tungstenite: snapview/tokio-tungstenite#313 TL;DR: we are using We should not use the re-exported version of The async version should not be affected |
…gstenite` Re-exported does not have the TLS fully functional if we only enable it on `tokio-tungstenite`, so a direct dependency is required
…gstenite` Re-exported does not have the TLS fully functional if we only enable it on `tokio-tungstenite`, so a direct dependency is required Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
…gstenite` Re-exported does not have the TLS fully functional if we only enable it on `tokio-tungstenite`, so a direct dependency is required Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
…ported from `tokio_tungstenite` Re-exported does not have the TLS fully functional if we only enable it on `tokio-tungstenite`, so a direct dependency is required Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
…o_tungstenite` (#4128) Signed-off-by: Nikita Strygin <dcnick3@users.noreply.github.com>
…-exported from `tokio_tungstenite`" This reverts commit 2c3a4ce.
Reported here: #4099 (comment) and in dev chat (https://t.me/c/1705484471/15317)
Seems to be a bug with cargo feature usage on tokio-tungstenite side. Investigating it...
The text was updated successfully, but these errors were encountered: