[
https://issues.apache.org/jira/browse/ARTEMIS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723131#comment-14723131
]
Jeff Mesnil commented on ARTEMIS-206:
-------------------------------------
I'm not sure it is working as expected. In your branch, NettyConnector is using
a hard-coded "http" URI during the HTTP upgrade handshake[1].
The issue reported against our application server is that this HTTP upgrade
should be done against the https URL when SSL is enabled.
[1]
https://github.com/jbertram/activemq-artemis/blob/ARTEMIS-206/artemis-core-client/src/main/java/org/apache/activemq/artemis/core/remoting/impl/netty/NettyConnector.java#L635
> HTTP Upgrade does not work over HTTPS
> -------------------------------------
>
> Key: ARTEMIS-206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-206
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.0.0
> Reporter: Jeff Mesnil
> Assignee: Justin Bertram
>
> For security reasons, we need to support creating Artemis connections over
> HTTPS Upgrade.
> Currently, the Upgrade code works only over HTTP.
> We need to also support it over HTTPS for increased security.
> This means that the NettyConnector code that deals with httpUpgradeEnabled
> must also check if sslEnabled is set.
> If that's the case, the GET request to upgrade the connection must be done
> over HTTPS instead of HTTP (and add Netty's SSLHandler to handle the SSL
> handshake)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
