Michall, A bit outside of the NiFi realm, but I have done similar myself previously. Do you have your server block (likely the one containing this location block) established with the appropriate certificates and a listen statement with ssl listed after the port? From memory, I do not believe any overwriting of the headers should be needed.
Is the problem strictly with NiFi? Are there any other services running where this is not an issue? On Mon, Mar 14, 2016 at 10:36 AM, michail salichos < [email protected]> wrote: > Hello, > > I followed the instructions here > > https://www.mail-archive.com/[email protected]/msg00566.html > > and managed to configure nginx as reverse proxy for HTTP, it works well. > > However, no matter what I tried I can't configure to terminate HTTPS on > nginx and then use plain HTTP to communicate with NIFI. This is the config > I am currently using for HTTP and it works > > location /nifi { > proxy_pass http://nifi:8080; > proxy_set_header X-ProxyScheme "http"; > proxy_set_header X-ProxyHost $http_host; > proxy_set_header X-ProxyPort 80; > proxy_set_header X-ProxyContextPath ""; > } > > I tried to change the scheme to HTTPS and port to 443 but no luck. > > Any tips or hints? > > > Regards, > Michail >
