-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Is your feature request related to a problem? Please describe.
Currently, the RabbitMQ AMQP 1.0 .NET Client only supports TCP-based connections. This limits usage in environments where raw TCP connections are restricted, but WebSockets are allowed (e.g., browsers using
frameworks like Blazor WebAssembly, corporate networks, certain cloud/PaaS platforms).
Describe the solution you'd like
Add support for AMQP 1.0 connections over WebSockets (ws:// / wss://) in the RabbitMQ AMQP 1.0 .NET Client.
The underlying library, AMQP.Net Lite, already supports WebSocket transports according to their GitHub README. Exposing or enabling this capability in the RabbitMQ client would allow users to leverage WebSockets without forking or re-implementing transport logic.
Describe alternatives you've considered
- Using AMQP.Net Lite directly instead of the RabbitMQ client (losing RabbitMQ-specific integrations).
- Using a different protocol entirely like MQTT over WebSocket.
- Forking the RabbitMQ AMQP 1.0 .NET Client to enable WebSocket transport directly.
None of these options are ideal for long-term maintenance or ecosystem consistency.
Additional context
Questions for maintainers:
- Is WebSocket transport intentionally unsupported?
- If not: Would a contribution adding this feature be welcome?
- And are there known architectural or security concerns with exposing this transport?