[ 
https://issues.apache.org/jira/browse/ARTEMIS-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445278#comment-17445278
 ] 

Marlon Müller commented on ARTEMIS-3574:
----------------------------------------

[~brusdev] Thanks for the clarification. I didn't thought about those scenarios 
as our artemis instances are only reachable within a private network. But I 
agree with you that there are use cases in which a reverse proxy is clearly the 
better choice.
Maybe it would be a good idea to state the intended use case of the embedded 
webserver more clearly in the documentation. At the moment it says: "However, 
it can also host other web applications like the REST interface or even 
Spring-based web applications (e.g. using Camel).". This could lead to the 
assumption to also run non-broker related applications on this server.

> Allow multiple bindings for embedded webserver
> ----------------------------------------------
>
>                 Key: ARTEMIS-3574
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3574
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Web Console
>    Affects Versions: 2.19.0
>            Reporter: Marlon Müller
>            Priority: Minor
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> At the moment it is only possible to configure one binding for the embedded 
> jetty webserver to listen on. It would be great to have the possibility to 
> configure multiple bindings for different war-files in order to serve those 
> files on different ports and allow the usage of http and https at the same 
> time.
> My current problem is the usage of the prometheus metrics plugin. In our 
> setup it is not possible to call the "/metrics" endpoint with SSL enabled. 
> Therefore I would like to define a second binding without SSL enabled for 
> this plugin. Disabling SSL completely is not an option as other endpoints 
> like the jolokia-api and the web-console require some user authentication 
> which should be protected.
> The idea is to move all binding related configuration parameters of the  
> "web" element and the configured "apps" in "bootstrap.xml" to a new element 
> called "binding" and put a list of those "binding" elements inside the "web" 
> element.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to