You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Akitoshi Yoshida (JIRA)" <ji...@apache.org> on 2015/03/19 16:41:38 UTC

[jira] [Commented] (CXF-6305) Add an option to include or exclude specific response headers in WebSocket's transport

    [ https://issues.apache.org/jira/browse/CXF-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369564#comment-14369564 ] 

Akitoshi Yoshida commented on CXF-6305:
---------------------------------------

pushed the relevant commit with the wrong issue number CXF-6232
master
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=commit;h=a79158c70fb2c8cedf109e78eeec32691a32e306

3.0.x
https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=commit;h=426dbdc11a70a32a92c581054df0abbf5cf098a7

> Add an option to include or exclude specific response headers in WebSocket's transport
> --------------------------------------------------------------------------------------
>
>                 Key: CXF-6305
>                 URL: https://issues.apache.org/jira/browse/CXF-6305
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 3.0.4
>            Reporter: Akitoshi Yoshida
>            Assignee: Akitoshi Yoshida
>             Fix For: 3.0.5
>
>
> When the application is returning a response with headers, currently only the content-type header is transferred back to the client over the WebSocket transport.
> This patch provides an option to include or exclude specific headers in the response.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)