qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPIDJMS-375) Enable setting of an "Authorization" Header during WebSocket connection handshake.
Date Wed, 25 Apr 2018 17:21:01 GMT

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

Timothy Bish resolved QPIDJMS-375.
----------------------------------
       Resolution: Fixed
         Assignee: Timothy Bish
    Fix Version/s: 0.32.0

QPIDJMS-384 Adds features that allow for this by using URI configuration or by injecting a
callback function that provides the HTTP headers to the WS Transport.

The URI can be configured via options such as "transport.ws.httpHeader.Authorization=FOO"

> 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
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 0.32.0
>
>
> 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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message