Proxying is typically used to distribute the load among several servers, seamlessly show content from different websites, or pass requests for processing to application servers over protocols other than HTTP.
When NGINX proxies a request, it sends the request to a specified proxied server, fetches the response, and sends it back to the client. It is possible to proxy requests to an HTTP server (another NGINX server or any other server) or a non-HTTP server (which can run an application developed with a specific framework, such as PHP or Python) using a specified protocol.
1. To pass a request to an HTTP proxied server, the proxy_pass directive is specified inside a location. For example:
|
1 2 3 |
location /some/path/ { proxy_pass http://www.example.com/link/; } |
2. This address can be specified as a domain name or an IP address. The address may also include a port:
|
1 2 3 |
location ~ \.php { proxy_pass http://127.0.0.1:8000; } |
3. To pass a request to a non-HTTP proxied server, the appropriate **_pass directive should be used:
- fastcgi_pass passes a request to a FastCGI server
- uwsgi_pass passes a request to a uwsgi server
- scgi_pass passes a request to an SCGI server
- memcached_pass passes a request to a memcached server
4. Passing Request Headers
|
1 2 3 4 5 |
location /some/path/ { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://localhost:8000; } |
5. To disable buffering in a specific location, place the proxy_buffering directive in the location with the off parameter, as follows:
|
1 2 3 4 |
location /some/path/ { proxy_buffering off; proxy_pass http://localhost:8000; } |