Rick, The signature of the endpoint that accepts a template upload has not changed (other than the path). Are you running a NiFi cluster in the trusted environment or is it a standalone instance? Is the issue when you attempt to upload the template or when you attempt to drop the template on your graph? Just wanted to confirm.
The mixed content error sounds like a client side message when a webpage is referencing resources (img, js, css, etc) from different sources. For instance, loading a webpage over HTTPS which is referencing a resource over HTTP. The frontend resources should all be bundled with the application and they should be all loaded through your proxy. Are there any other errors or messages? Maybe check the user log on the NiFi instances. Or maybe the logs of the proxy server to see the requests being processed. Hoping there's more details being logged someplace. Thanks Matt On Wed, Dec 14, 2016 at 1:11 PM, Richard St. John <[email protected]> wrote: > I am using an nginx reverse proxy in front of NiFi 1.1.x. Here are the > important details. First, nginx is using basic auth and SSL. Second, NiFi > is running in a trusted environment without SSL. We successfully used the > same layout for NiFi 0.7.x without issue. However, starting with 1.0.x and > continuing in 1.1.x, I cannot import a saved template. The error complains > about mixed content (http and https). Has this layout been tested and > validated? If so, what proxy headers am I missing? > > Below are the proxy headers I pass from nginx to NiFi: > proxy_set_header X-ProxyScheme $scheme; > proxy_set_header X-ProxyHost $host; > proxy_set_header X-ProxyPort 443; > proxy_set_header X-ProxyContextPath ""; > > > Thanks Rick. > -- > > ---------------------------- > Richard St. John, Ph.D. > Senior Software Engineer, Applied Mathematician > Asymmetrik, Ltd. >
