Shulou(Shulou.com)06/01 Report--

How to use Location to implement routing reverse proxy in Nginx? in order to solve this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

I. Common settings

1. Log format

Log_format main'$time_iso8601 | $remote_addr | $remote_user | $request_method | $uri |''$status | $request_time | $request_length | $body_bytes_sent | $bytes_sent |''$connection | $http_x_forwarded_for | $upstream_addr | $upstream_status |''$upstream_response_time | $args | $http_referer | $http_user_agent';access_log logs/access.log main

2. Reverse proxy transparently transfers client IP settings

Proxy_set_header Host $http_host;proxy_set_header X-Real-IP $remote_addr;proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for

3. Global variables

The variable $args # is equal to the parameter in the request line. The Content-length field in the $content_length # request header. The Content-Type field in the $content_type # request header. $document_root # the value specified in the root directive is currently requested. $host # requests the host header field, otherwise it is the server name. $http_user_agent # client agent information $http_cookie # client cookie information $limit_rate # this variable can limit the connection rate. $request_body_file # temporary file name of the client requesting principal information. $request_method # the action requested by the client, usually GET or POST. $remote_addr # the IP address of the client. Port of the $remote_port # client. $remote_user # user name that has been authenticated by Auth Basic Module. $request_filename # the file path of the current request, generated by the root or alias directive and the URI request. $query_string # is the same as $args. The $scheme # HTTP method (such as http,https). The protocol used by the $server_protocol # request, usually HTTP/1.0 or HTTP/1.1. $server_addr # server address, which can be determined after completing a system call. $server_name # server name. $server_port # the port number where the request arrives at the server. $request_uri # contains the original URI of the request parameter, without the hostname, such as "/ foo/bar.php?arg=baz". $uri # the current URI,$uri without request parameters does not contain a hostname, such as "/ foo/bar.html". $document_uri # is the same as $uri.

II. Rewrite rules

Syntax: rewrite regular replacement flag bit

Flag tag (the last parameter of the rewrite directive):

1.last last terminates the rewrite detection of the current location, but continues to retry location matching and process the rewrite rules in the block.

2.break break terminates the rewrite detection of the current location and no longer performs location matching.

3.redirect returns 302 temporary redirection, and the browser address displays the URL address after the jump.

4.permanent returns 301 permanent redirection, and the browser address displays the URL address after the jump.

Example:

# regular match location ~ ^ / (a | bb | ccc) / {rewrite ^ / ([amurz] +) / (. *) $http://106.185.48.229/$2?$1;}# Note: the parameter enclosed in parentheses is the following $1 $2 variable

Third, the routing strategy of reverse proxy

Configuration of Location:

Syntax:

Location [= | ~ | ~ * | ^ ~] / uri/ {… }

Syntax description:

The beginning of = indicates an exact match, and regularities are not supported.

The beginning of ^ ~ means that uri begins with a regular string and does not support regularities. It can be understood as matching the url path.

The beginning of ~ and ~ * indicates a case-sensitive and case-insensitive regular match.

The beginning of! ~ and! ~ * indicates a regular match that is case-sensitive and case-insensitive.

/ Universal match, any request will match, usually at the end of the configuration.

Match priority:

= > ^ ~ > ~, * > empty

Full matching > path matching > regular matching > string matching

Example:

# string matching location / static {alias / home/www/static; access_log off;} # path match, when the end of proxy_pass / decides whether to take the matching path location ^ / 333 / {proxy_pass http://106.185.48.229/;}# regular match, the proxy_pass cannot end / location ~ ^ / (xxx | yyy) / {proxy_pass http://106.185.48.229; } # string match, when the end of proxy_pass / determines whether to take the matching path location / zzz/ {proxy_pass http://106.185.48.229/;}# default matches location / {proxy_pass http://127.0.0.1:8080; } this is the answer to the question about how to use Location to implement routing reverse proxy in Nginx. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.