[
https://issues.apache.org/jira/browse/ARTEMIS-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17987209#comment-17987209
]
Gašper Čefarin commented on ARTEMIS-5559:
-----------------------------------------
No, I was not aware of this. I tried it just now, results are the same.
If this is still a step in the right direction, it should be added in the
default jolokia-access.xml file.
jolokia-access.xml:
{code:java}
<restrict>
<cors>
<allow-origin>*</allow-origin>
</cors>
<!-- Use if Origin header can use https while the protocol is http (e.g.,
with TLS proxy) -->
<ignore-scheme/>
</restrict>
{code}
Do you have any other ideas?
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
