tink_http
tink_http copied to clipboard
Make client side distinction between http and https less awkward.
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.