Advanced Nginx Configuration Techniques for Security, Logging, and Traffic Management

Nginx is widely known for its high performance, stability, friendly configuration, rich modules, and active open‑source community. Developed by Russian engineer Igor Sysoev, its market share in the web‑server field has been steadily increasing, reaching 33.3% according to a 2017 W3Techs report.

This article assumes readers are already familiar with basic installation, configuration, and optimization, and focuses on practical features for special business scenarios.

Custom Version Information

Hiding version details can raise the attack barrier. You can either modify the source file src/core/nginx.h to change the version string, or simply hide the version in the runtime configuration by setting server_tokens off; in nginx.conf.

Custom 404 Page

The default 404 page can be replaced in two ways: (1) create a 404.html file in the site root, or (2) use the error_page directive to redirect to an external page, e.g. error_page 404 = http://www.37.com/404.html; Log Format to JSON

Standard Nginx logs are plain text, which becomes hard to process at terabyte scale. By redefining the log_format directive in nginx.conf, you can output logs in JSON, making downstream processing with other languages much easier.

Client‑Based Request Handling

Using built‑in variables such as $remote_addr and $http_user_agent, you can add rewrite or conditional logic to treat requests differently based on client IP or User‑Agent.

Modify Download File Name

To force a download with a custom filename without exposing the real file name, add a response header:

add_header Content-Disposition "attachment;filename=$name.exe";

This technique also helps identify which server handled a request when many servers are behind a load balancer.

Rate Limiting for High Traffic

When a sudden traffic surge occurs, Nginx can limit request rates using the limit_zone and limit_req_zone modules. For example, limiting $server_name to 600 requests per second with a burst of 1000, returning a 400 status for excess requests.

Traffic Mirroring

Since version 1.13.4, Nginx supports traffic mirroring via the ngx_http_mirror_module. A mirror sub‑request can be created to duplicate the original request for testing or analysis.

Other useful Nginx features such as upstream configuration and web caching are also available. For further learning, refer to the official Nginx website, book list, and development guide links provided at the end of the article.