Configurer un proxy inverse simple

In simple terms, a reverse proxy acts as an intermediary between clients (like your web browser) and your backend servers. When you send a request, it goes to the reverse proxy first.

The reverse proxy then forwards your request to the appropriate backend server, collects the response, and sends it back to you. It's like a helpful receptionist for your web services!

Nginx (pronounced "engine-x") is a popular, high-performance web server that can also function as a very efficient reverse proxy.

It sits at the "edge" of your network, receiving all incoming client requests. Based on its configuration, Nginx decides which backend application or server should handle the request.

Think of it as a traffic cop, directing incoming requests to the correct destination.

Nginx configurations are organized into blocks. The primary block for handling incoming connections is the server block.

Each server block defines a virtual host, specifying:

• The port Nginx listens on (listen directive).
• The domain names it responds to (server_name directive).

It's where Nginx decides which specific application configuration to use for a given request.

Inside a server block, you use location blocks to define how Nginx should handle requests for specific URLs or URL patterns.

For example, a location / {} block matches all requests, while a location /api {} block matches requests starting with /api.

This allows you to route different parts of your application to different backend services.

The magic directive for reverse proxying is proxy_pass. This directive tells Nginx where to forward the incoming request.

You place proxy_pass inside a location block. Its value is the URL of your backend server or application.

• http://localhost:8080: A local web server.
• http://my-backend-service.com: A remote service.

Nginx will take the client's request and send it directly to this specified URL.

Let's create a simple Nginx configuration to proxy requests. We'll set Nginx to listen on port 80 and forward all requests to a backend application running on localhost:8080.

This hides the backend's port and allows Nginx to handle public traffic.

When Nginx proxies a request, it acts on behalf of the client. By default, some original client information (like their IP address) might be lost or replaced by Nginx's own details.

To preserve this information, we use proxy_set_header directives. Key headers to set include:

• Host: Original requested host.
• X-Real-IP: The client's actual IP address.
• X-Forwarded-For: A list of proxy IPs, including the client's.
• X-Forwarded-Proto: The original protocol (HTTP/HTTPS).

These headers are crucial for backend applications to correctly identify the client and handle requests.

It's good practice to include essential headers in your reverse proxy configuration. This helps your backend application receive the correct client information.

Here's our previous example, updated with common proxy_set_header directives.

Even a basic reverse proxy setup offers significant advantages:

• Security: Hides the backend server's direct IP and port from the public.
• Load Distribution: (Even for one server, it prepares for more).
• SSL Termination: Nginx can handle HTTPS encryption, offloading the backend.
• URL Rewriting: Present a cleaner URL to clients while internally routing to complex paths.

This single point of entry simplifies management and enhances control over traffic.

Consider the following Nginx configuration snippet. Which directive is used to forward client requests to a backend server?

server {
listen 80;
server_name example.com;
location / {
# THIS IS WHERE THE DIRECTIVE GOES
http://my-backend-app:9000;
}
}

Great job! You've learned the fundamentals of configuring Nginx as a simple reverse proxy.

We covered:

• The role of server and location blocks.
• Using proxy_pass to forward requests.
• The importance of proxy_set_header for preserving client information.

This foundational knowledge is key to building more complex and robust Nginx setups. Next, we'll explore how to manage multiple backend servers!