Nginx is a high-performance WEB server. In addition to Apache, Tomcat, Jetty and IIS, they are all WEB servers, or World Wide WEB (WWW) servers, and have the basic functions of WEB servers accordingly. What advantages does Nginx have over other WEB services?
Tomcat and Jetty are heavyweight WEB servers for the Java language, and their performance is not comparable to Nginx.
IIS runs only on Windows operating systems. Windows is less stable as a server than uniX-like operating systems in terms of stability and other performance, so IIS is not superior in situations where a high-performance Web server is required.
Apache development period is long, and it is now arguably the world’s first big Web server, it has many advantages, such as stability, open source, cross-platform, but it appears the time is too long, the rise of the s, the Internet industry scale than today, so it is designed to become a leading, the Web server does not support high concurrency. On the Apache server, if tens of thousands of concurrent HTTP requests are accessed at the same time, the server will consume a lot of memory. Switching between hundreds of Apache processes by the operating system kernel will consume a lot of CPU resources and reduce the average response speed of HTTP requests. All of this made It impossible for Apache to become a high-performance Web server, which led to the emergence of Lighttpd and Nginx. The chart below shows the strong growth momentum for 18 years.
1.2 Compilation and Installation
Installation environment Preparations:
(1) Linux kernel 2.6 and later:
Epool was only supported after 2.6. Prior to that, the USE of SELECT or Pool multiplexing IO models did not solve the problem of high concurrency pressures. To view the information, run the uname -a command.
# Check the Linux kernel uname -aCopy the code
(2) GCC compiler
GNU Compiler Collection (GCC) is used to compile C programs. Nginx does not provide binary executables directly, only the source code can be downloaded and compiled.
(3) PCRE library
PCRE (Perl Compatible Regular Expressions) is a library developed by Philip Hazel that supports Regular Expressions.
(4) Zlib library
The zlib library is used to compress the contents of HTTP packages in gzip format, if we configure gzip on in nginx.conf and specify gzip for some content-type HTTP responses to reduce network traffic.
(5) OpenSSL development library
If our server is not only going to support HTTP, but also needs to transport HTTP over the more secure SSL protocol, then we need to have OpenSSL. Also, if we want to use hash functions such as MD5 and SHA1, we need to install it. The above libraries are all necessary for the basic functionality of Nginx. For simplicity, we can install them using the yum command.
#yum install make zlib zlib-devel GCC c++ libtool openssl openssl-devel pcre pcre-devel #yum install zlib-devel GCC c++ libtool openssl openssl-devel pcreCopy the code
Source code:
Nginx download page: nginx.org/en/download… .
Nginx # download the latest stable version of wget http://nginx.org/download/nginx-1.19.1.tar.gz # extract tar - ZXVF nginx - 1.19.1. Tar. GzCopy the code
Easiest installation:
/configure make && make installCopy the code
The nginx run file is installed in /usr/local/nginx.
Parameter-based construction
./configure --prefix=/usr/local/nginx --with-http_stub_status_module --with-http_ssl_module --with-debug
Copy the code
Control command:
# default boot mode: /sbin/nginx -c/TMP /nginx.conf # Specify the nginx program directory to start./sbin/nginx -p /usr/local/nginx /sbin/nginx -s reload # Reopen the file./sbin/nginx -s reload # reopen the file./sbin/nginx -s reloadCopy the code
1.3 Module Updates
The following uses the third-party ngx_HTTP_google_filter_module module as an example.
Nginx modules are required to recompile Nginx, rather than configuration files referencing.so like Apache
Download the third-party extension module ngx_http_google_filter_module
# cd /data/software/
# git clone https://github.com/cuber/ngx_http_google_filter_module
Copy the code
See which modules are installed when nginx is compiled and installed
Switch the command line to the directory where the Nginx executable resides and type./ Nginx -v as follows:
[root@hjh sbin]# ./nginx -V nginx version: Nginx /1.19.1 BUILT by GCC 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC) Built with OpenSSL 1.0.2 22 Jan 2015 TLS SNI support enabled configure arguments: -- prefix = / usr/local/nginx 1.19.1 - with - openssl = / usr/local/SRC/openssl - 1.0.2 - with - pcre = / usr/local/SRC/pcre - 8.37 - with - zlib = / usr/local/SRC/zlib - 1.2.8 - with - http_ssl_module [root @ HJH sbin] #Copy the code
You can see that the following parameters are used to compile and install Nginx:
-- prefix = / usr/local/nginx 1.19.1 - with - openssl = / usr/local/SRC/openssl - 1.0.2 - with - pcre = / usr/local/SRC/pcre - 8.37 - with - zlib = / usr/local/SRC/zlib - 1.2.8 - with - http_ssl_moduleCopy the code
Note here: Do not execute the make install command.
Replace nginx binaries
/usr/local/nginx-1.19.1/sbin/nginx /usr/local/nginx-1.19.1/sbin/nginx.bak Copy the newly compiled nginx executable to /usr/local/nginx-1.19.1/sbin/ # cp /opt/ nginx-sbin/nginx /usr/local/nginx-1.19.1/sbin/Copy the code
2. Nginx architecture description
2.1 Nginx architecture Diagram
2.2 Architecture Description
When nginx starts, it generates two types of processes: a Master process, one (currently only one on Windows), and multiple Worker processes. The main process does not handle network requests, but schedules worker processes, which are the three shown here: loading configuration, starting worker processes, and non-stop upgrades. So, after nginx is started, if you look at the operating system process list, you can see that there are at least two Nginx processes.
The server actually handles network requests and responds to worker processes. On unix-like systems, Nginx can be configured with multiple workers, and each worker process can handle thousands of network requests at the same time.
Modular design. Nginx worker includes core and functional modules. The core module is responsible for maintaining a run-loop and performing module functions at different stages of network request processing, such as network read and write, storage read and write, content transfer, outgoing filtering, and sending requests to upstream servers. The modular design of its code also makes it possible for us to select and modify the functional modules appropriately according to needs and compile them into servers with specific functions.
Event-driven, asynchronous, and non-blocking are key to nGINx’s high concurrency and high performance, as well as the adoption of event notification and I/O performance enhancements such as Kqueue, Epoll, and Event ports in Linux, Solaris, and BSD-like operating system kernels.
Events, HTTP, server, location and upstream in the above configuration belong to the configuration item block. Worker_processes, worker_connections, include, and LISTEN are attributes in the configuration item block. / nginx_STATUS specifies a parameter parameter that belongs to the configuration block. The Server block is nested in the HTTP block and can directly inherit and access the parameters in the HTTP block.
The configuration block
A name begins with a large number wrapped around its corresponding property
attribute
Based on the whitespace split attribute name and attribute value, the attribute value may have multiple entries split by Spaces, such as access_log logs/host.access.log main
parameter
It is configured between the block name and braces, and is separated by Spaces if there are more than one value
Notice If the value of a configuration item contains a syntax symbol, such as a space character, use single or double quotation marks to enclose the value. Otherwise, Nginx will report a syntax error. Such as:
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
Copy the code
3.2 Configuring the first static WEB service
Basic site demo:
Create the site directory mkdir -p /usr/www/test
Writing a static file
Configure nginx. Conf
Configure the server
Configure the location
Basic configuration description:
(1) Listening port
Syntax: Listen address:
Default: listen 80;
Configuration block: Server
Server_name name[…] ;
Default: server_name “”;
Configuration block: Server
Server_name can be followed by multiple host names, such as server_name www.testweb.com and download.testweb.com. . Supports wildcard and re characters
(3) the location
Grammar: the location [= | | | ~ ~ * ^ ~ | @] / uri / {… }
Configuration block: Server
= indicates that the URI is taken as a string to match exactly the URI in the parameter.
/ Based on uri directory matching.
~ indicates that the re is case-sensitive when matching urIs.
~ * indicates that case is ignored when matching urIs.
^ ~ indicates that only the first half of the re matches the URI parameter.
Static and static separation demonstration:
Creating a Static site
Configure the location/static
Configuration ~ *. (GIF | PNG | | js, CSS) $
Dynamic and static separation based on directory
server { listen 80; server_name *.test.com; root /usr/www/test; location / { index test.html; } location /static { alias /usr/www/static; }}Copy the code
Based on regular static and static separation
location ~* \.(gif|jpg|png|css|js)$ {
root /usr/www/static;
}
Copy the code
Anti-theft chain configuration demonstration:
Valid_referers None blocked *.test.com; if ($invalid_referer) { return 403; }Copy the code
