You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/rewrite-http-headers.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ You use rewrite actions to specify the request and response headers that you wan
51
51
52
52
## Server variables
53
53
54
-
Application Gateway uses server variables to store useful information about the server, the connection with the client, and the current request on the connection. Examples of information stored include the client’s IP address and the web browser type. Server variables change dynamically, for example, when a new page loads or when a form is posted. You can use these variables to evaluate rewrite conditions and rewrite headers.
54
+
Application Gateway uses server variables to store useful information about the server, the connection with the client, and the current request on the connection. Examples of information stored include the client’s IP address and the web browser type. Server variables change dynamically, for example, when a new page loads or when a form is posted. You can use these variables to evaluate rewrite conditions and rewrite headers. In order to use the value of server variables to rewrite headers, you will need to specify these variables in the syntax {var_*serverVariable*}
55
55
56
56
Application gateway supports these server variables:
57
57
@@ -64,20 +64,21 @@ Application gateway supports these server variables:
64
64
| client_port | The client port. |
65
65
| client_tcp_rtt | Information about the client TCP connection. Available on systems that support the TCP_INFO socket option. |
66
66
| client_user | When HTTP authentication is used, the user name supplied for authentication. |
67
-
| host | In this order of precedence: the host name from the request line, the host name from the Host request header field, or the server name matching a request. |
67
+
| host | In this order of precedence: the host name from the request line, the host name from the Host request header field, or the server name matching a request. Example: in the request *http://contoso.com:8080/article.aspx?id=123&title=fabrikam*, host value will be is *contoso.com*|
68
68
| cookie_*name*| The *name* cookie. |
69
69
| http_method | The method used to make the URL request. For example, GET or POST. |
70
70
| http_status | The session status. For example, 200, 400, or 403. |
71
71
| http_version | The request protocol. Usually HTTP/1.0, HTTP/1.1, or HTTP/2.0. |
72
-
| query_string | The list of variable/value pairs that follows the "?" in the requested URL. |
72
+
| query_string | The list of variable/value pairs that follows the "?" in the requested URL. Example: in the request *http://contoso.com:8080/article.aspx?id=123&title=fabrikam*, query_string value will be *id=123&title=fabrikam*|
73
73
| received_bytes | The length of the request (including the request line, header, and request body). |
74
74
| request_query | The arguments in the request line. |
75
75
| request_scheme | The request scheme: http or https. |
76
-
| request_uri | The full original request URI (with arguments). |
76
+
| request_uri | The full original request URI (with arguments). Example: in the request *http://contoso.com:8080/article.aspx?id=123&title=fabrikam*, request_uri value will be */article.aspx?id=123&title=fabrikam*|
77
77
| sent_bytes | The number of bytes sent to a client. |
78
78
| server_port | The port of the server that accepted a request. |
79
79
| ssl_connection_protocol | The protocol of an established TLS connection. |
80
80
| ssl_enabled | “On” if the connection operates in TLS mode. Otherwise, an empty string. |
81
+
| uri_path | Identifies the specific resource in the host that the web client wants to access. This is the part of the request URI without the arguments. Example: in the request *http://contoso.com:8080/article.aspx?id=123&title=fabrikam*, uri_path value will be */article.aspx*|
0 commit comments