activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harmen Renkema (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-6766) HttpsClientTransport broken when port isn't explicitly included in the broker url
Date Mon, 10 Jul 2017 14:58:00 GMT
Harmen Renkema created AMQ-6766:
-----------------------------------

             Summary: HttpsClientTransport broken when port isn't explicitly included in the
broker url
                 Key: AMQ-6766
                 URL: https://issues.apache.org/jira/browse/AMQ-6766
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.14.3
            Reporter: Harmen Renkema


In the HttpsClientTransport in the createSchemeRegistry method on line 51 a new Scheme is
instantiated. The port fed to the constructor of Scheme is gotten from the remoteUrl URI,
which will be set to -1 if the port wasn't explicitly included in the broker url.

The code should be able to deal with this scenario. For instance fallback to 443 when the
port on the URI is undefined.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message