As websocket does not specify an authentication mechanism, I'm probably going to use standard http(s) authentication (e.g., username/password) or token. Is it possible to do this through the ClientBuilder API or do I have to use a separate method such as HttpClientCodec?
I want to re-use the TLS stream and possibly any cookies or headers set by the server.
As websocket does not specify an authentication mechanism, I'm probably going to use standard http(s) authentication (e.g., username/password) or token. Is it possible to do this through the ClientBuilder API or do I have to use a separate method such as
HttpClientCodec?I want to re-use the TLS stream and possibly any cookies or headers set by the server.