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

ASF GitHub Bot commented on QPIDJMS-375:
----------------------------------------

GitHub user mibo opened a pull request:

    https://github.com/apache/qpid-jms/pull/18

    QPIDJMS-375: Added transport.ws.authorizationHeader option

    As described in the JIRA item: 
https://issues.apache.org/jira/browse/QPIDJMS-375
    
    According tests will follow (however the {{NettyWsTransportTest}} and 
{{NettyEchoServer}} seems to fit not perfect for my test case).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mibo/qpid-jms QPIDJMS-375

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-jms/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #18
    
----
commit 7c7703204209f2fef5cbbeda59f732a2983db7ba
Author: mibo <mibo@...>
Date:   2018-04-06T03:31:19Z

    QPIDJMS-375: Added transport.ws.authorizationHeader option

----


> Enable setting of an "Authorization" Header during WebSocket connection 
> handshake.
> ----------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-375
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-375
>             Project: Qpid JMS
>          Issue Type: New Feature
>          Components: qpid-jms-client
>            Reporter: Michael Bolz
>            Priority: Major
>
> Add support for setting of an "Authorization" Header during WebSocket 
> connection handshake.
> This "Authorization" Header will be passed via the "transport" parameters 
> (TransportOptions).
> Proposed transport is {{transport.ws.authorizationHeader}}.
> I will create a "Pull Request" and link it here.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to