Installing NGINX and Third-Party Modules
[ 14 ]
Option Explanation
--http-log-path=<path> The default path to the HTTP access log.
--http-client-body-temp-
path=<path>
When receiving the request from the client,
this is the directory used as a temporary
location for the body of that request.
If the WebDAV module is enabled, it is
recommended to set this path to be on the
same filesystem as the final destination.
--http-proxy-temp-
path=<path>
When proxying, this is the directory used
as a location to store temporary files.
--http-fastcgi-temp-
path=<path>
The location for FastCGI temporary files.
--http-uwsgi-temp-
path=<path>
The location for uWSGI temporary files.
--http-scgi-temp-
path=<path>
The location for SCGI temporary files.
Enabling various modules
Besides the http and mail modules, there are a number of other modules included in the
NGINX distribution. These modules are not activated per default, but may be enabled by
setting the appropriate configuration option --with-
Table: HTTP module configure options
Option Explanation
--with-http_ssl_module If you need to encrypt web traffic, you will need
this option to be able to use URLs beginning
with https. (Requires the OpenSSL library.)
--with-http_realip_module If your NGINX will be behind a L7 load balancer
or other device that passes the client's IP address
in an HTTP header, you will need to enable this
module. For use in situations where multiple
clients appear to come from one IP address.
--with-http_addition_module This module works as an output filter, enabling
you to add content of a different location before
or after that of the location itself.
--with-http_xslt_module This module will handle transformations of
XML responses, based on one or more XSLT
stylesheets. (Requires the libxml2 and libxslt
libraries.)