


How to use Nginx as a reverse proxy to configure GZip compression
Prerequisites: node.js nginx reverse proxy.
node.js Work that needs to be done:
express 4.0 or below:
app.use(express.compress()); //主要是这句 app.use(express.json()); app.use(express.urlencoded()); app.use(express.bodyparser()); app.use(express.methodoverride()); app.use(express.cookieparser());
In order to allow all requests Compression, so compress is placed on top.
express 4.0 and above (including 4.0)
var compress = require('compression'); app.use(compress());
4.0 and above versions take out the middleware independently.
So you first need to rquire('compression')
Click here to view the main differences between express 3.5 and express 4.0
The work that node.js needs to do is so simple.
nginx needs to do Work:
Open the nginx configuration file, modify the configuration, and turn on the gzip switch
nano /usr/local/nginx/conf/nginx.conf
The nginx on your own server may not be installed in the /usr/local/ directory, so according to your own installation directory Find the configuration file nginx.conf
Add the following configuration to the http configuration node:
gzip on; gzip_min_length 1k; gzip_buffers 4 16k; gzip_http_version 1.0; gzip_comp_level 2; gzip_types text/plain application/x-javascript text/css application/xml; gzip_vary on; http ( //放上面配置节点 )
What does each configuration item mean?
1) gzip
Syntax: gzip on/off
Default value: off
Scope: http, server, location
Description: Turn on or off the gzip module, use on here to indicate Start
2) gzip_min_length
Syntax: gzip_min_length length
Default value: gzip_min_length 0
Scope: http, server, location
Description: Set the minimum number of bytes of the page that is allowed to be compressed. The number of bytes of the page is obtained from the content-length in the header. The default value is 0, which compresses the page regardless of its size. It is recommended to set the number of bytes to be greater than 1k. If it is less than 1k, it may become more and more compressed. |
3) gzip_buffers
Syntax: gzip_buffers number size
Default value: gzip_buffers 4 4k/8k
Scope: http, server, location
Description: Set the system to obtain several units of cache for storing the gzip compression result data stream. 4 16k means to apply for memory in units of 16k and 4 times the original data size in units of 16k.
4) gzip_comp_level
Syntax: gzip_comp_level 1..9
Default value: gzip_comp_level 1
Scope: http, server, location
Description: gzip compression ratio, 1 has the smallest compression ratio and the fastest processing speed, 9 has the largest compression ratio but the slowest processing (fast transmission but consumes more CPU). Here it is set to 5.
5) gzip_types
Syntax: gzip_types mime-type [mime-type ...]
Default value: gzip_types text/html
Scope : http, server, location
Description: Match the mime type for compression, (whether specified or not) the "text/html" type will always be compressed. This is set to application/x-javascript text/css application/xml.
There are commonly used static types, depending on the situation you need to compress:
text/html text/plain text/css application/x-javascript text/javascript application/xml
ok, the basic server has been configured here, nginx only needs to reload.
Let’s test how to use curl to test that gzip has been turned on on the server (the test condition is the default gzip_types, that is, only text.html is compressed, and other types are not compressed):
Check whether it is turned on gzip, the client needs to add: "accept-encoding: gzip, deflate" header information.
$ curl -i -h "accept-encoding: gzip, deflate" "http://localhost/tag.php"
http/1.1 200 ok server: nginx date: thu, 08 mar 2012 07:23:46 gmt content-type: text/html connection: close content-encoding: gzip
$ curl -i -h "accept-encoding: gzip, deflate" "http://localhost/style.css"
http/1.1 200 ok server: nginx date: thu, 08 mar 2012 07:23:54 gmt content-type: text/css connection: close last-modified: tue, 27 dec 2011 10:00:51 gmt etag: "bc612352322d435769c4bdc03ddb2572" content-length: 22834
You can see it. The second example is not compressed.
The above is the detailed content of How to use Nginx as a reverse proxy to configure GZip compression. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To allow the Tomcat server to access the external network, you need to: modify the Tomcat configuration file to allow external connections. Add a firewall rule to allow access to the Tomcat server port. Create a DNS record pointing the domain name to the Tomcat server public IP. Optional: Use a reverse proxy to improve security and performance. Optional: Set up HTTPS for increased security.

The start and stop commands of Nginx are nginx and nginx -s quit respectively. The start command starts the server directly, while the stop command gracefully shuts down the server, allowing all current requests to be processed. Other available stop signals include stop and reload.

Steps to run ThinkPHP Framework locally: Download and unzip ThinkPHP Framework to a local directory. Create a virtual host (optional) pointing to the ThinkPHP root directory. Configure database connection parameters. Start the web server. Initialize the ThinkPHP application. Access the ThinkPHP application URL and run it.

To register for phpMyAdmin, you need to first create a MySQL user and grant permissions to it, then download, install and configure phpMyAdmin, and finally log in to phpMyAdmin to manage the database.

Server deployment steps for a Node.js project: Prepare the deployment environment: obtain server access, install Node.js, set up a Git repository. Build the application: Use npm run build to generate deployable code and dependencies. Upload code to the server: via Git or File Transfer Protocol. Install dependencies: SSH into the server and use npm install to install application dependencies. Start the application: Use a command such as node index.js to start the application, or use a process manager such as pm2. Configure a reverse proxy (optional): Use a reverse proxy such as Nginx or Apache to route traffic to your application

To solve the "Welcome to nginx!" error, you need to check the virtual host configuration, enable the virtual host, reload Nginx, if the virtual host configuration file cannot be found, create a default page and reload Nginx, then the error message will disappear and the website will be normal show.

nginx appears when accessing a website. The reasons may be: server maintenance, busy server, browser cache, DNS issues, firewall blocking, website misconfiguration, network connection issues, or the website is down. Try the following solutions: wait for maintenance to end, visit during off-peak hours, clear your browser cache, flush your DNS cache, disable firewall or antivirus software, contact the site administrator, check your network connection, or use a search engine or web archive to find another copy of the site. If the problem persists, please contact the site administrator.

There are five methods for container communication in the Docker environment: shared network, Docker Compose, network proxy, shared volume, and message queue. Depending on your isolation and security needs, choose the most appropriate communication method, such as leveraging Docker Compose to simplify connections or using a network proxy to increase isolation.
