Skip to content

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

@back2dos

Description

@back2dos

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions