You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Paul Galbraith (Jira)" <ji...@apache.org> on 2021/07/09 12:51:00 UTC

[jira] [Resolved] (CAMEL-16739) camel-websocket - Provide connection relative path for routing

     [ https://issues.apache.org/jira/browse/CAMEL-16739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Galbraith resolved CAMEL-16739.
------------------------------------
    Fix Version/s: 3.12.0
       Resolution: Implemented

> 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
>             Fix For: 3.12.0
>
>
> If the endpoint 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)