[
https://issues.apache.org/jira/browse/NIFI-9469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17456734#comment-17456734
]
David Handermann commented on NIFI-9469:
----------------------------------------
Thanks for describing the issue [~porterep]. The {{NiFiProperties}} class
includes a method to normalize the context path that explicitly trims context
path values that begin and end with a forward slash, which happens to be the
case in this situation.
Based on the configuration described, it sounds like the reverse proxy
configuration provides access to NiFi using the root context path without
performing URL rewriting. If that is the desired configuration, the
{{X-ProxyContextPath}} should not be necessary since the request path should be
the same as what the proxy receives. If you avoid setting the
{{X-ProxyContextPath}} request header on your proxy server, you should not need
to set the {{nifi.web.proxy.context.path}} property. Does that work with your
environment?
> 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)
