[
https://issues.apache.org/jira/browse/CXF-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973078#comment-13973078
]
Sergey Beryozkin commented on CXF-5698:
---------------------------------------
Hi Aki,
Thanks for the explanation, right I see what you mean now.
I propose we keep this issue open because this restriction can be a problem,
even though it is reasonable to expect the client know the initial endpoint
address ending with "/bookstore" and consider introducing a property such as
"endpoint.address" which will let the transport correctly determine the actual
root during the upgrade
Cheers, Sergey
> Use the service root path instead of the initial request path to restrict
> websocket service access
> --------------------------------------------------------------------------------------------------
>
> Key: CXF-5698
> URL: https://issues.apache.org/jira/browse/CXF-5698
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 3.0.0
>
>
> Currently, the URL path used to initiate the websocket connection is used to
> allow or restrict the subsequent operations received over the websocket.
> This is not convenient as the caller must know the service root path to be
> able to invoke all the operations supported by the service. A more convenient
> approach would be to use the service root path as the filter so that the
> subsequent requests to one of its operations can be processed even if the
> initial connection request uses one of these sub resource paths.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
