Greetings, I have deployed a single node unsecured NiFi cluster (I say cluster because nifi.cluster.is.node is set to "true") as a stateful set on Kubernetes (AWS EKS to be specific). The NiFi cluster sits behind an Nginx ingress. I have configured the Nginx ingress to forward the appropriate headers to NiFi (when deployed behind a reverse proxy) as described in the documentation <https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration>.
The path on the Nginx ingress which proxies traffic to the NiFi UI is "/pie/ip". This same path has been whitelisted by setting the "nifi.web.proxy.context.path" property to "/pie/ip". The way I am expecting this setup to work is that when users navigate to http://foo.com/pie/ip <http://foo.com/pie/ip> in the browser, they are shown a simple HTML page with redirect info and then automatically redirected to http://foo.com/pie/ip/nifi <http://foo.com/pie/ip/nifi> where they can view the NiFi canvas. Instead, the users are being redirected to http://foo.com/nifi <http://foo.com/nifi> which results in a 404 response because there is no '/nifi' path that has been configured on the Nginx ingress. I set the NiFi and Jetty Server log levels to DEBUG to understand what was happening under the hood and this is what I got - On Startup (when the SanitizeContextPathFilter is initialized) - 2019-10-11 06:07:26,206 DEBUG [main] o.a.n.w.filter.SanitizeContextPathFilter SanitizeContextPathFilter received provided whitelisted context paths from NiFi properties: /pie/ip On Request (when the actual request is made) - 2019-10-11 06:45:45,556 DEBUG [NiFi Web Server-23] org.apache.nifi.web.util.WebUtils Context path: 2019-10-11 06:45:45,556 DEBUG [NiFi Web Server-23] org.apache.nifi.web.util.WebUtils On the request, the following context paths were parsed from headers: X-ProxyContextPath: /pie/ip X-Forwarded-Context: null X-Forwarded-Prefix: null 2019-10-11 06:45:45,556 DEBUG [NiFi Web Server-23] org.apache.nifi.web.util.WebUtils Determined context path: /pie/ip 2019-10-11 06:45:45,556 ERROR [NiFi Web Server-23] org.apache.nifi.web.util.WebUtils The provided context path [/pie/ip] was not whitelisted  2019-10-11 06:45:45,556 ERROR [NiFi Web Server-23] org.apache.nifi.web.util.WebUtils Error determining context path on JSP page: The provided context path [/pie/ip] was not whitelisted  2019-10-11 06:45:45,556 DEBUG [NiFi Web Server-23] o.a.n.w.filter.SanitizeContextPathFilter SanitizeContextPathFilter set contextPath: You will notice from the above log entries that the path '/pie/ip' was successfully whitelisted. Yet, when handling the request, the whitelisted context paths array is empty and this causes the wrong redirect to happen on the browser - and I can't figure out why this is happening or how I can fix it. Has anyone come across this kind of problem before? Any help on this is much appreciated. Cheers, Swarup.