[
https://issues.apache.org/jira/browse/FELIX-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340670#comment-16340670
]
Jörg Hoh commented on FELIX-5767:
---------------------------------
Ok. But is there any intent to change the behavior, so the webconsole can be
bound to more than 1 http context? I could clearly see the benefits in that
(e.g. binding it only to contexts which are reachable from internal networks,
while not binding it to the http context serving to the public).
> Webconsole binds only to a single HTTP context
> ----------------------------------------------
>
> Key: FELIX-5767
> URL: https://issues.apache.org/jira/browse/FELIX-5767
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-4.2.18, webconsole-4.3.4
> Reporter: Jörg Hoh
> Priority: Major
>
> I want my application to be reachable by 2 different ways:
> * localhost via http (for easy maintenance)
> * on network interfaces only via https
> Therefor I created 2 different HTTP contexts, configured them accordingly and
> everything worked fine. But the webconsole was reachable only via 1 context.
> The description for the property "http.service.filter" of the "Apache Felix
> OSGI Management console" component states:
> {code}
> By default (if this property is not set or set to an emptystring) the Web
> Console binds with any Http Service available.
> {code}
> This doesn't seem to be the case. Also checking the code make me think, that
> the webconsole is only bound to a single (random) http context by default.
> But I need the webconsole reachable via more than 1 http context.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
