[
https://issues.apache.org/jira/browse/ARTEMIS-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987267#comment-17987267
]
Gašper Čefarin commented on ARTEMIS-5559:
-----------------------------------------
You're right - I didn't put it inside cors node. My bad on this one.
I can confirm it works on haproxy as well.
But just to confirm we're talking about the same thing - I am using http scheme
on jetty. Ignoring the scheme when exposed via a proxy isn't less secure than
exposing jetty via http. It's just less secure than terminating the SSL at
jetty side.
This update (on jetty's side ...) broke the setup. But the broker config could
at the very least add a commented out option. I think it's fair to expect
admins won't necessarily be reading jetty upgrade notes when bumping artemis.
> Cannot proxy traffic to jolokia when SSL is terminated
> ------------------------------------------------------
>
> Key: ARTEMIS-5559
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5559
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Reporter: Gašper Čefarin
> Priority: Major
> Attachments: jolokia_403.png, results2.png
>
>
> A problem appeared when upgrading from 2.37 to 2.41. I strongly suspect it
> happens when upgrading from jetty 11 to 12.
> This is one of the only visible problems - response from
> {{https://xxxxxxxxxx/console/jolokia}} (actual http response is 200)
> !jolokia_403.png|width=75%!
> This is how the "console" looks:
> !results2.png|width=75%!
> I was not able to find a solution yet which would work with haproxy.
> Exposing via jetty only works fine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
