[
https://issues.apache.org/jira/browse/CAMEL-16738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Galbraith updated CAMEL-16738:
-----------------------------------
Issue Type: Improvement (was: New Feature)
> Support for websocket subprotocols
> ----------------------------------
>
> Key: CAMEL-16738
> URL: https://issues.apache.org/jira/browse/CAMEL-16738
> Project: Camel
> Issue Type: Improvement
> Components: camel-websocket
> Reporter: Paul Galbraith
> Priority: Minor
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
