Edgardo, 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 pass through accordingly. For instance, if you only mapped the /nifi context path, the custom ui for Update Attributes 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. This is why your able to view the graph, but you cannot modify anything. It attempting to call back directly to your NiFi, not through your proxy. 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 I've never done the proxying through nginx so please let me know if this helps. Matt On Thu, Sep 10, 2015 at 6:04 PM, Edgardo Vega <[email protected]> wrote: > I am trying to setup Nifi unsung nginx as a reverse proxy. I would like > nginx to terminate the ssl connection and then run nifi on http. I have > tried to set it up but ran into an issue were any viewing operation works > but cannot make any changes (move, start, stop, etc). The browser complains > about mixed content. > > So how do you configure nifi to work correctly in this scenario? > > > -- > Cheers, > > Edgardo > > Sent from Gmail Mobile >
