Skip to content

error if transport is not supported #8

Description

@robertkowalski

Lets say I run a setup with HTTP transports

Given my client uses accidentally the WS transport, it will just idle endlessly, waiting for an answer.

Expected behaviour: Error message that the current transport is (probably?) not available

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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