Book Image

Nginx Troubleshooting

By : Alexey Kapranov
Book Image

Nginx Troubleshooting

By: Alexey Kapranov

Overview of this book

Nginx is clearly winning the race to be the dominant software to power modern websites. It is fast and open source, maintained with passion by a brilliant team. This book will help you maintain your Nginx instances in a healthy and predictable state. It will lead you through all the types of problems you might encounter as a web administrator, with a special focus on performance and migration from older software. You will learn how to write good configuration files and will get good insights into Nginx logs. It will provide you solutions to problems such as missing or broken functionality and also show you how to tackle performance issues with the Nginx server. A special chapter is devoted to the art of prevention, that is, monitoring and alerting services you may use to detect problems before they manifest themselves on a big scale. The books ends with a reference to error and warning messages Nginx could emit to help you during incident investigations.
Table of Contents (15 chapters)
Nginx Troubleshooting
About the Author
About the Reviewers
Rare Nginx Error Messages

Apache migration problems

One of the Apache features that Nginx chose not to replicate is the support for the so-called .htaccess files. Those files were invented as a way to easily configure access control for individual virtual hosts in a virtual hosting environment where clients are only able to see their own subfolders via the magic of chroot (often called from ftpd). The implementation is rather simple; this is an autoincluded piece of configuration that Apache constantly monitors for changes. Not every possible Apache configuration directive is allowed in .htaccess (but many of them are, essentially, all that do not require a restart).

This feature was (ab)used as a convenient way to distribute the relevant web server configuration inside the source code for a website or a web application. Although the idea is still relevant, the Apache implementation with a silent change monitoring and transparent reconfiguration is not considered well designed. So, instead of the proper .htaccess...