[
https://issues.apache.org/jira/browse/NIFI-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473076#comment-17473076
]
Gilles Perreault commented on NIFI-9469:
----------------------------------------
Hi
Same issue:
{quote}javax.ws.rs.core.UriBuilderException: The provided context path [/] was
not registered as allowed [[]]
{quote}
Upgrading from 1.9.2 to 1.15.2, I have the exact same problem as described in
this JIRA. The 1.9.2 is working fine, no issue with the proxy configuration
(which was not changed in the upgrade process).
I've tried the proposed solution: remove the {{X-ProxyContextPath line in the
apache2rpxy configuration and leave the nifi.web.proxy.context.path empty,
without any luck...}}
NOTE: after removing the {{X-ProxyContextPath}} line, the old 1.9.2 no longer
worked, so I put it back...
P.S. this is my first "collaboration" here, so don't be afraid to point me in
the proper direction if I'm not using the right channel.
> Context path issue when NiFi is served behind proxy server
> ----------------------------------------------------------
>
> Key: NIFI-9469
> URL: https://issues.apache.org/jira/browse/NIFI-9469
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 1.15.0
> Environment: CentOS 7, openjdk version "1.8.0_312"
> Reporter: Eric Porter
> Priority: Minor
> Labels: proxy
>
> After upgrading to NiFi 1.15.0 we noticed that we could no longer reach nifi
> on the root context path. The error we were seeing follows:
> {noformat}
> javax.ws.rs.core.UriBuilderException: The provided context path [/] was not
> registered as allowed [[]] {noformat}
> Our nifi.web.proxy.context.path was set to:
> {noformat}
> nifi.web.proxy.context.path=/{noformat}
>
> To troubleshoot, we added /nifi to the nifi.web.proxy.context.path property
> and changed our X-ProxyContextPath proxy setting to "/nifi" and found that we
> could load nifi.
> {noformat}
> nifi.web.proxy.context.path=/nifi,/
> X-ProxyContextPath "/nifi"{noformat}
> However, leaving X-ProxyContentPath set to "/" and setting
> nifi.web.proxy.context.path=/nifi,/ resulted in the same error, but helped us
> to discover that there seems to be an issue with parsing the single '/'
> character from the nifi.web.proxy.context.path setting.
> {code:java}
> javax.ws.rs.core.UriBuilderException: The provided context path [/] was not
> registered as allowed [[/nifi, ]] {code}
> After trying different escaping methods, were able to work around this issue
> by using the following setting:
> {noformat}
> nifi.web.proxy.context.path=//{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
