[
https://issues.apache.org/jira/browse/ARTEMIS-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino resolved ARTEMIS-2899.
--------------------------------------------------
Fix Version/s: 2.16.0
Resolution: Fixed
> Make Artemis console reverse proxy friendly
> -------------------------------------------
>
> Key: ARTEMIS-2899
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2899
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Web Console
> Affects Versions: 2.15.0
> Reporter: Stephan Austermühle
> Assignee: Andy Taylor
> Priority: Major
> Fix For: 2.16.0
>
>
> We are running an Artemis cluster inside of a Kubernetes cluster and want to
> expose the broker web console via a Kubernetes Ingress. This currently works
> only when using a dedicated host and exposing the root url but not for
> sub-paths (e.g., {{/my/path/console}}) because the console path is hardcoded
> to the second element in {{index.html}}:
> {code:js}
> <script type="text/javascript">
> var base = window.location.pathname.split('/', 2)[1];
> if (base == "") {
> document.write("<base href='/'/>");
> } else {
> document.write("<base href='/" + base + "/' />");
> }
> </script>
> {code}
> Changing the the url in {{bootstrap.xml}} is not an option because
> applications accessing the Jolokia interface then need to know the external
> address.
--
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
