


Nginx reverse proxy sets domain name and elegantly implements forwarding
Nginx reverse proxy sets domain name and elegantly implements forwarding
Overview
In web development, we often encounter situations where a proxy is required to forward requests. As a high-performance web server, Nginx can forward requests through reverse proxy, thereby achieving efficient load balancing and dynamic configuration.
The basic principle of Nginx reverse proxy is to send the request from the client to the Nginx server, and then the Nginx server forwards the request to the back-end server that actually processes the request. By setting the domain name, we can implement different proxy forwarding rules for requests from different domain names.
Set the domain name
To implement proxy forwarding of the domain name, you first need to configure the domain name resolution. Suppose we have two domain names that need to be forwarded, namely www.example1.com and www.example2.com. We can resolve these two domain names to the IP address of the Nginx server on the DNS service provider's console.
Next, we need to set the proxy forwarding rules for the domain name in the Nginx configuration file. Open the Nginx configuration file, usually located at /etc/nginx/nginx.conf, find the server block, and then configure the corresponding domain name and forwarding rules in the server block.
The sample code is as follows:
server { listen 80; server_name www.example1.com; location / { proxy_pass http://backend1; proxy_set_header Host $host; } } server { listen 80; server_name www.example2.com; location / { proxy_pass http://backend2; proxy_set_header Host $host; } }
In the above code, we first define a server block, set the listen command to listen to port 80, and the server_name command sets the domain name to www.example1.com . The configuration directive proxy_pass in the location block specifies that the forwarding target of the request is http://backend1. The proxy_set_header directive sets the Host field of the request header to $host, which is to maintain the authenticity of the request.
Similarly, we add another server block, set server_name to www.example2.com, and proxy_pass to http://backend2.
Configuring forwarding targets
In the above configuration, we use backend1 and backend2 as forwarding targets. These two targets refer to the address of the backend server, which can be a domain name, IP address, or UNIX domain socket.
To associate these two forwarding targets with the backend server that actually handles the request, we need to add an upstream block within the http block of the Nginx configuration file. The sample code is as follows:
http { upstream backend1 { server backend1.example.com; } upstream backend2 { server backend2.example.com; } }
In the above code, we define two upstream blocks to associate the address of the backend server with backend1 and backend2 through the server directive. Among them, backend1.example.com and backend2.example.com are the addresses of the backend servers that actually handle the request.
Restart Nginx
After completing the configuration of the domain name and forwarding target, we need to restart the Nginx server to make the configuration take effect. Enter the following command in the terminal to restart:
sudo service nginx restart
Then, you can test whether the forwarding is set correctly by visiting www.example1.com and www.example2.com.
Summary
By setting the domain name and forwarding rules, we can implement Nginx's reverse proxy and forward requests to different back-end servers. This allows you to flexibly configure forwarding rules and achieve efficient load balancing and dynamic configuration. At the same time, Nginx also provides a wealth of modules and functions, which can further expand the capabilities of reverse proxy and meet more needs.
The above is the detailed content of Nginx reverse proxy sets domain name and elegantly implements forwarding. For more information, please follow other related articles on the PHP Chinese website!

NGINX and Apache have their own advantages and disadvantages and are suitable for different scenarios. 1.NGINX is suitable for high concurrency and low resource consumption scenarios. 2. Apache is suitable for scenarios where complex configurations and rich modules are required. By comparing their core features, performance differences, and best practices, you can help you choose the server software that best suits your needs.

Question: How to start Nginx? Answer: Install Nginx Startup Nginx Verification Nginx Is Nginx Started Explore other startup options Automatically start Nginx

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

To shut down the Nginx service, follow these steps: Determine the installation type: Red Hat/CentOS (systemctl status nginx) or Debian/Ubuntu (service nginx status) Stop the service: Red Hat/CentOS (systemctl stop nginx) or Debian/Ubuntu (service nginx stop) Disable automatic startup (optional): Red Hat/CentOS (systemctl disabled nginx) or Debian/Ubuntu (syst

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.


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

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

Zend Studio 13.0.1
Powerful PHP integrated development environment

SublimeText3 English version
Recommended: Win version, supports code prompts!

SublimeText3 Chinese version
Chinese version, very easy to use

Dreamweaver Mac version
Visual web development tools