Websocket: multi-connection TLS multiplexing

[weiyixuan]

Whether multi-connection TLS reuse is supported? If not, will it be implemented in the future?

[IngCr3at1on]

To my understanding (and admittedly this is something I just read up on before answering here so I may have missed something); multiplexed TLS requires the DTLS protocol which is not implemented in the STL. There is a Go DTLS implementation floating around but based on the age I'm pretty sure anything done around the TLS support in Gorilla would predate its existence.

Interestingly the RFC for TLS multiplexing appears to be in draft stage and has expired...

Edit: to be clear this is more of an "I'm honestly not sure but I don't think so" than a "no" :joy:

[elithrar]

Browsers don’t support DTLS for WebSockets - only for WebRTC. Which isn’t
abnormal - DTLS has very specific applications.

Saying that - I’d want to understand the use-case backing the ask anyway -
are these browser clients? Custom clients? What drives the multiplexing
need at the TLS level?

On Tue, Jul 9, 2019 at 11:18 AM Nathan Bass [e-mail]
wrote:

To my understanding (and admittedly this is something I just read up on
before answering here so I may have missed something); multiplexed TLS
requires the DTLS protocol which is not implemented in the STL. There is a
Go DTLS implementation floating around but based on the age I'm pretty sure
anything done around the TLS support in Gorilla would predate its existence.

Interesting the RFC for TLS multiplexing appears to be in draft stage and
has expired...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gorilla/websocket/issues/521?email_source=notifications&email_token=AAAEQ4HLGCUGNT2ETCKZZ43P6S25VA5CNFSM4H7EFAQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQY35I#issuecomment-509709813,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEQ4HXWQVNLLKJYRPP2ELP6S25VANCNFSM4H7EFAQQ
.

[weiyixuan]

Is a custom client, not a browser client. WSS connection between client and server needs to be established frequently. In order to improve the speed, it is hoped to do connection reuse in TLS layer.

[ghost]

It is not appropriate for this package to directly support the feature because there is not a standard for the feature, nor do browsers support the feature.

Applications can implement the feature using the NetDialContext hook.