Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
I would like to see camel-websocket support subprotocols as per RFC 6455, during connection upgrade negotiation. Ideally we could specify the subprotocol(s) that our application supports via a subprotocol option in the component/endpoint URI. If camel-websocket accepts a subprotocol proposed by a connecting client, then the client should be informed of the agreed subprotocol via HTTP header (as per RFC 6455), and the agreed subprotocol should also be provided as a message header via the camel-subprotocol consumer.
Attachments
Issue Links
- links to