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
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Directive Reference
Persisting Solaris Network Tunings
Index

Converting an if-fy configuration to a more modern interpretation


Using the if directive within a location is really only considered valid for certain cases. It may be used in combination with a return and with a rewrite directive with a last or break flag, but should generally be avoided in other situations. This is due in part to the fact that it can produce some very unexpected results. Consider the following example:

location / {

  try_files /img /static @imageserver;

  if ($request_uri ~ "/blog") {

    proxy_pass http://127.0.0.1:9000;

    break;

  }

  if ($request_uri ~ "/tickets") {

    proxy_pass http://tickets.example.com;

    break;
  }

}

location @imageserver {

  proxy_pass http://127.0.0.1:8080;
}

Here, we're trying to determine which upstream to pass the request to, based on the value of the $request_uri variable. This seems like a very reasonable configuration at first glance, because it works for our simple test cases. But the images will neither be served from the...