Re: Hosting API's on Nifi

definitely ignore my suggestion - i didn't read the question properly. If you want to use a single port to address multiple applications you'll need something a little more capable than simply port forwarding. On Thu, Mar 2, 2017 at 2:30 PM, Joe Gresock wrote: > I believe the

Re: Hosting API's on Nifi

I believe the traditional approach would be to specify another port like 8443 in the NiFi HandleHttpRequest processor, and use a reverse proxy like nginx or httpd running on 80/443 that directs traffic to NiFi. We have done this on our own project, and there are several articles floating around

Re: Hosting API's on Nifi

You can run the processor on another port and use port forwarding to go from 80 to whatever port you're really using. This is a good practice anyway since you don't want to run nifi as root ideally (you could also allow nifi to bind to lower ports, but..). Lots of ways to slice it. Thanks joe

Re: Hosting API's on Nifi

Anil Aside from opening another port I don’t se how you can overcome this issue. HandleHttpRequest essentially starts another web server and this server needs a port to listen on. Further more, there are many other network based Processors that come with NiFi that would fall int the same

Hosting API's on Nifi

Hello All, I am exposing an API using HandleHttpRequest on my local nifi instance. The HandleHttpRequest processor requires a Listening port that I need to provide. If I enter 80 in that field, the processor fails when it starts saying “unable to initialize the server”. Which is expected