[
https://issues.apache.org/jira/browse/QPIDJMS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bolz updated QPIDJMS-375:
---------------------------------
Description:
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}}.
According "[Pull Request|https://github.com/apache/qpid-jms/pull/18]";
was:
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.
> 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}}.
> According "[Pull Request|https://github.com/apache/qpid-jms/pull/18]";
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
