-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Description
Summary
So I'm currently debugging paritytech/substrate#12024 and what I found is I don't really understand how secure WS transport (/wss) is supposed to work.
I give it an address like /dns/polkadot-boot.dwellir.com/tcp/443/wss/p2p/<nodeID> and expect it to connect. However, I get an error saying invalid multi-address: /dns/polkadot-boot.dwellir.com/tcp/443/p2p/<nodeID> address is invalid from inner TCP transport. Am I supposed to supply DNS as an inner transport if I want to support /wss addresses? Documentation is rather scarse.
Expected behaviour
I'd expect for WSS transport to work kinda.
Actual behaviour
Possible Solution
Use DNS transport as inner T when creating WSS transport.
Version
0.50.0
Would you like to work on fixing this bug?
Yes
Metadata
Metadata
Assignees
Labels
No labels