Book Image

Mastering NGINX - Second Edition

By : Dimitri Aivaliotis
Book Image

Mastering NGINX - Second Edition

By: Dimitri Aivaliotis

Overview of this book

NGINX is a high-performance HTTP server and mail proxy designed to use very few system resources. But despite its power it is often a challenge to properly configure NGINX to meet your expectations. Mastering Nginx is the solution – an insider’s guide that will clarify the murky waters of NGINX’s configuration. Tune NGINX for various situations, improve your NGINX experience with some of the more obscure configuration directives, and discover how to design and personalize a configuration to match your needs. To begin with, quickly brush up on installing and setting up the NGINX server on the OS and its integration with third-party modules. From here, move on to explain NGINX's mail proxy module and its authentication, and reverse proxy to solve scaling issues. Then see how to integrate NGINX with your applications to perform tasks. The latter part of the book focuses on working through techniques to solve common web issues and the know-hows using NGINX modules. Finally, we will also explore different configurations that will help you troubleshoot NGINX server and assist with performance tuning.
Table of Contents (20 chapters)
Mastering NGINX - Second Edition
About the Author
About the Reviewer
Directive Reference
Persisting Solaris Network Tunings


The SPDY protocol was developed by Google to accelerate the web browsing experience. There are currently four drafts; the final one supported in NGINX labeled Draft 3.1. NGINX supported this draft as of version 1.5.10.

The protocol developers also had a hand in the ratification of HTTP/2. SPDY has since been deprecated; all support for it will end in 2016. It is superseded by HTTP version 2 (HTTP/2), which NGINX has supported since version 1.9.5.

Support for HTTP/2 can be activated by including the compile-time flag, --with-http_v2_module. This will make the following directives available for configuration:

HTTP/2 directives



This directive sets the maximum chunk size for the response body.


This directive specifies the amount of time with no activity after which the connection is closed.


This directive sets the number of HTTP/2 streams that may be active in a single connection.