[
https://issues.apache.org/jira/browse/AMQ-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082836#comment-16082836
]
Timothy Bish commented on AMQ-6766:
-----------------------------------
Please provide the simplest possible unit test demonstrating the issue
> 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)
