[
https://issues.apache.org/jira/browse/NIFI-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643937#comment-17643937
]
Julien G. commented on NIFI-8820:
---------------------------------
This feature is still needed.
When we want to port forward in docker/K8s environment we can't.
And if we cant to put the NiFi Registry behind Istio we can't either.
> NiFi Registry should implement context path verification similar to NiFi
> ------------------------------------------------------------------------
>
> Key: NIFI-8820
> URL: https://issues.apache.org/jira/browse/NIFI-8820
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Registry
> Reporter: Koji Kawamura
> Priority: Major
>
> NIFIREG-295 makes NiFi Registry can be accessed behind a reverse proxy. In
> such deployments NiFi Registry can be accessed with a context path configured
> at the reverse proxy.
> NiFi API verifies context path at WebUtils.verifyContextPath() using white
> listed context paths configured at 'nifi.web.proxy.context.path' in
> nifi.properties.
> NiFi Registry API should do the same context path verification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
