Sign In Start Free Trial

NGINX Cookbook

By : Tim Butler

3.3 (4)

NGINX Cookbook

3.3 (4)

By: Tim Butler

Overview of this book

NGINX Cookbook covers the basics of configuring NGINX as a web server for use with common web frameworks such as WordPress and Ruby on Rails, through to utilization as a reverse proxy. Designed as a go-to reference guide, this book will give you practical answers based on real-world deployments to get you up and running quickly. Recipes have also been provided for multiple SSL configurations, different logging scenarios, practical rewrites, and multiple load balancing scenarios. Advanced topics include covering bandwidth management, Docker container usage, performance tuning, OpenResty, and the NGINX Plus commercial features. By the time you've read this book, you will be able to adapt and use a wide variety of NGINX implementations to solve any problems you have.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Sections

Conventions

Reader feedback

Customer support

Free Chapter

Let's Get Started

Let's Get Started

Introduction

A quick installation guide

Configuring NGINX

Enabling modules

Deploying a basic site

Basic monitoring

Real-time statistics

Common PHP Scenarios

Common PHP Scenarios

Introduction

Configuring NGINX for WordPress

WordPress multisite with NGINX

Running Drupal using NGINX

Using NGINX with MediaWiki

Using Magento with NGINX

Configuring NGINX for Joomla

Common Frameworks

Common Frameworks

Introduction

Setting up Django with NGINX

Setting up NGINX with Express

Running Ruby on Rails with NGINX

Easy Flask with NGINX

Laravel via NGINX

Meteor applications with NGINX

High speed Beego with NGINX

All About SSLs

All About SSLs

Introduction

Basic SSL certificates

Enabling HTTP/2 on NGINX

Configuring HSTS in NGINX

Easy SSL certificates with Let's Encrypt

Making NGINX PCI DSS compliant

OCSP stapling with NGINX

Achieving full A+ Qualys rating

Logging

Logging

Introduction

Logging to syslog

Customizing web access logs

Virtual host log format

Application focused logging

Logging TLS mode and cipher information

Logging POST data

Conditional logging

Using the Elastic Stack

Rewrites

Rewrites

Introduction

Redirecting non-www to www-based sites

Redirecting to a new domain

Blocking malicious user agents

Redirecting all calls to HTTPS to secure your site

Redirecting pages and directories

Redirecting 404 errors through a search page

Reverse Proxy

Reverse Proxy

Introduction

Configuring NGINX as a simple reverse proxy

Content caching with NGINX

Monitoring cache status

Microcaching

Serving from cache when your backend is down

SSL termination proxy

Rate limiting

Load Balancing

Load Balancing

Introduction

Round robin load balancing

Least connected load balancing

Hash-based load balancing

Testing and debugging NGINX load balancing

TCP / application load balancing

NGINX as an SMTP load balancer

Advanced Features

Advanced Features

Introduction

Authentication with NGINX

WebDAV with NGINX

Bandwidth management with NGINX

Connection limiting with NGINX

Header modification with NGINX

Docker Containers

Docker Containers

Introduction

NGINX web server via Docker

NGINX reverse proxy via Docker

Docker Compose with NGINX

NGINX load balancing with Docker

Performance Tuning

Performance Tuning

Introduction

Gzipping content in NGINX

Enhancing NGINX with keep alive

Tuning worker processes and connections

Fine tuning basic Linux system limits

Integrating ngx_pagespeed

OpenResty

OpenResty

Introduction

Installing OpenResty

Getting started with OpenResty Lua

Lua microservices with OpenResty

Simple hit counter with a Redis backend

Powering API Gateways with OpenResty

NGINX Plus – The Commercial Offering

NGINX Plus – The Commercial Offering

Introduction

Installing NGINX Plus

Real-time server activity monitoring

Dynamic config reloading

Session persistence

Customer Reviews

3.3 (4)

5 star

25%

4 star

25%

3 star

0

2 star

50%

1 star

0

Hash-based load balancing

When you need to ensure that hash-based load balancing is the optimal choice, commonly, the client's IP address is used as the pattern to match so that any issues with cookies and per upstream server session tracking is sticky. This means that every subsequent request from the same hash will always route to the same upstream server (unless there's a fault with the upstream server).

How to do it...

The upstream block directive looks exactly the same as the round-robin configuration, except we now explicitly tell NGINX to use the hash method—a reminder that this needs to remain outside of the server block directive. Here's our upstream block:

upstream localapp { 
    hash $remote_addr...

Search

Your notes and bookmarks