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
At the moment, iroh clients that connect to a relay via websockets do so using the tokio_tungstenite_wasm library, which doesn't support providing your own AsyncRead/AsyncWrite, so you're not in control of connection establishment (which makes sense because in the browser you don't have control over that).
We should vendor the WebSocketStream library used in tokio_tungstenite_wasm and add our own enum case for a connection where we do provide our own AsyncRead/AsyncWrite (MaybeTlsStreamReader/Writer specifically) and have control over connection establishment.
This enables:
HTTP proxy support when connecting to a relay over websockets
Writing tests that excercise relay-over-WSS (with TLS, but faked certificates)
At the moment, iroh clients that connect to a relay via websockets do so using the
tokio_tungstenite_wasm
library, which doesn't support providing your ownAsyncRead/AsyncWrite
, so you're not in control of connection establishment (which makes sense because in the browser you don't have control over that).We should vendor the
WebSocketStream
library used intokio_tungstenite_wasm
and add our own enum case for a connection where we do provide our ownAsyncRead/AsyncWrite
(MaybeTlsStreamReader
/Writer
specifically) and have control over connection establishment.This enables:
Context: #2387 (comment)
The text was updated successfully, but these errors were encountered: