[
https://issues.apache.org/jira/browse/CAMEL-16739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16739:
--------------------------------
Summary: camel-websocket - Provide connection relative path for routing
(was: Provide connection relative path for routing)
> camel-websocket - Provide connection relative path for routing
> --------------------------------------------------------------
>
> Key: CAMEL-16739
> URL: https://issues.apache.org/jira/browse/CAMEL-16739
> Project: Camel
> Issue Type: Improvement
> Components: camel-websocket
> Reporter: Paul Galbraith
> Priority: Minor
>
> If the enpoint URI specifies a wildcard for accepting connections, then after
> a client establishes a connection the relative path of that connection should
> be provided by the consumer in a message header.
> E.g. if my endpoint is _websocket://0.0.0.0:80/application/*_ and a client
> connects using URL _ws://host.com/application/customer/profile_, then the
> relative path _customer/profile_ should be provided in a message header for
> potential custom routing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
