[
https://issues.apache.org/jira/browse/NIFI-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938157#comment-15938157
]
Matt Gilman commented on NIFI-3638:
-----------------------------------
[~RTJarvis] Just wanted to clarify which URLs you were referring?
There are a couple of key items to know when standing up NiFi behind a proxy.
1) NiFi is comprised of a number of web applications (web ui, web api,
documentation, custom ui's, etc). So you'll need to set up your mapping to the
root path. That way all context paths are passed through accordingly. For
instance, if you only mapped the /nifi context path, the custom ui for
UpdateAttribute will not work since it's available at
/update-attribute-ui-<version>.
2) NiFi's rest api will generate uri's for each component on the graph. Since
your coming through a proxy, you'll need to override certain elements of the
uri's being generated. You can override the elements of the uri by adding the
following HTTP headers when your proxy generates the HTTP request to the NiFi
instance:
X-ProxyScheme - the scheme to use to connect to your proxy (https in this case)
X-ProxyHost - the host of your proxy
X-ProxyPort - the port your proxy is listening on
X-ProxyContextPath - the path you've configured to map to the NiFi instance
> Absolute URLs in jQuery calls
> ------------------------------
>
> Key: NIFI-3638
> URL: https://issues.apache.org/jira/browse/NIFI-3638
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.1.1
> Reporter: Richard Jarvis
> Priority: Minor
>
> When running NiFi behind a proxy, all URLs should be relative. If they are
> not relative, there should be a configuration to override the host name.
> To reproduce:
> Run NiFi behind a proxy
> Add a component to a blank Flow
> Click on configure.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
