Skip to content
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

Using ClientBuilder For HTTP Authentication #164

Open
git-blame opened this issue Feb 12, 2018 · 0 comments
Open

Using ClientBuilder For HTTP Authentication #164

git-blame opened this issue Feb 12, 2018 · 0 comments

Comments

@git-blame
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant