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

Make client side distinction between http and https less awkward. #119

Open
back2dos opened this issue Apr 28, 2020 · 0 comments
Open

Make client side distinction between http and https less awkward. #119

back2dos opened this issue Apr 28, 2020 · 0 comments

Comments

@back2dos
Copy link
Member

Selecting a client for a URL is quite a daunting task, and the distinction provides little value.

For containers, the existence of secure versions makes quite a lot of sense, because they require additional configuration to function properly.

For clients, I would go as far as erasing the distinction. Where HTTPS is not supported, it should provide a proper error. Where HTTPS specifics can be configured, the client should allow doing so via the constructor.

kevinresol added a commit that referenced this issue Aug 25, 2020
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