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

Jean-Baptiste Onofré commented on KARAF-7536:
---------------------------------------------

It's confirmed: it's related to Jetty upgrade: 
https://github.com/eclipse/jetty.project/commit/9a14de058da715f2d08c2bff58b548a39045ea85

> jolokia-access.xml stopped working in 4.4.1
> -------------------------------------------
>
>                 Key: KARAF-7536
>                 URL: https://issues.apache.org/jira/browse/KARAF-7536
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.4.1
>            Reporter: Rastislav Papp
>            Assignee: Jean-Baptiste Onofré
>            Priority: Critical
>
> We use jolokia-osgi with access restricted via jolokia-access.xml, specifying 
> that only localhost (or 127.0.0.1) is allowed.
> After upgrading to karaf 4.4.1, all jolokia requests return http 403, because 
> {{getRemoteHost}} method of 
> {{org.ops4j.pax.web.service.spi.servlet.OsgiHttpServletRequestWrapper}} now 
> returns {{"[127.0.0.1]"}} instead of {{"127.0.0.1"}}. A hotfix was to add new 
> entries to jolokia-access.xml, with the IPs wrapped with [], but I suspect 
> other functionality might be broken because of this.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to