Web Properties

These properties pertain to the web-based User Interface.


Property	Description
nifi.web.war.directory	This is the location of the web war directory. The default value is `./lib`.
nifi.web.http.host	The HTTP host. It is blank by default.
nifi.web.http.port	The HTTP port. The default value is `8080`.
nifi.web.http.port.forwarding	The port which forwards incoming HTTP requests to `nifi.web.http.host`. This property is designed to be used with 'port forwarding', when NiFi has to be started by a non-root user for better security, yet it needs to be accessed via low port to go through a firewall. For example, to expose NiFi via HTTP protocol on port 80, but actually listening on port 8080, you need to configure OS level port forwarding such as `iptables` (Linux/Unix) or `pfctl` (OS X) that redirects requests from 80 to 8080. Then set `nifi.web.http.port` as 8080, and `nifi.web.http.port.forwarding` as 80. It is blank by default.
nifi.web.http.network.interface*	The name of the network interface to which NiFi should bind for HTTP requests. It is blank by default.NOTE: Multiple network interfaces can be specified by using the *nifi.web.http.network.interface.* prefix with unique suffixes and separate network interface names as values. For example, to provide two additional network interfaces, a user could also specify additional properties with keys of: nifi.web.http.network.interface.eth0=eth0 nifi.web.http.network.interface.eth1=eth1 Providing three total network interfaces, including `nifi.web.http.network.interface.default`.
nifi.web.https.host	The HTTPS host. It is blank by default.
nifi.web.https.port	The HTTPS port. It is blank by default. When configuring NiFi to run securely, this port should be configured.
nifi.web.https.port.forwarding	Same as `nifi.web.http.port.forwarding`, but with HTTPS for secure communication. It is blank by default.
nifi.web.https.network.interface*	The name of the network interface to which NiFi should bind for HTTPS requests. It is blank by default.NOTE: Multiple network interfaces can be specified by using the *nifi.web.https.network.interface.* prefix with unique suffixes and separate network interface names as values. For example, to provide two additional network interfaces, a user could also specify additional properties with keys of: nifi.web.https.network.interface.eth0=eth0 nifi.web.https.network.interface.eth1=eth1 Providing three total network interfaces, including `nifi.web.https.network.interface.default`.
nifi.web.jetty.working.directory	The location of the Jetty working directory. The default value is `./work/jetty`.
nifi.web.jetty.threads	The number of Jetty threads. The default value is `200`.
nifi.web.max.header.size	The maximum size allowed for request and response headers. The default value is 16 KB.
nifi.web.proxy.host	A comma separated list of allowed HTTP Host header values to consider when NiFi is running securely and will be receiving requests to a different host[:port] than it is bound to. For example, when running in a Docker container or behind a proxy (e.g. localhost:18443, proxyhost:443). By default, this value is blank meaning NiFi should only allow requests sent to the host[:port] that NiFi is bound to.
nifi.web.proxy.context.path	A comma separated list of allowed HTTP X-ProxyContextPath or X-Forwarded-Context header values to consider. By default, this value is blank meaning all requests containing a proxy context path are rejected. Configuring this property would allow requests where the proxy path is contained in this listing.