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