Merge pull request #190930 from JackStromberg/patch-45

adding 6th value

Author: PRMerger3

articles/application-gateway/how-application-gateway-works.md

@@ -53,11 +53,11 @@ When an application gateway sends the original request to the backend server, it
 
 ### Modifications to the request
 
-Application gateway inserts five additional headers to all requests before it forwards the requests to the backend. These headers are x-forwarded-for, x-forwarded-proto, x-forwarded-port, x-original-host, and x-appgw-trace-id. The format for x-forwarded-for header is a comma-separated list of IP:port.
+Application gateway inserts six additional headers to all requests before it forwards the requests to the backend. These headers are x-forwarded-for, x-forwarded-port, x-forwarded-proto, x-original-host, x-original-url, and x-appgw-trace-id. The format for x-forwarded-for header is a comma-separated list of IP:port.
 
 The valid values for x-forwarded-proto are HTTP or HTTPS. X-forwarded-port specifies the port where the request reached the application gateway. X-original-host header contains the original host header with which the request arrived. This header is useful in Azure website integration, where the incoming host header is modified before traffic is routed to the backend. If session affinity is enabled as an option, then it adds a gateway-managed affinity cookie.
 
-x-appgw-trace-id is a unique guid generated by application gateway for each client request and presented in the forwarded request to the backend pool member.  The guid consists of 32 alphanumeric characters presented without dashes (for example: ac882cd65a2712a0fe1289ec2bb6aee7). This guid can be used to correlate a request received by application gateway and initiated to a backend pool member via the transactionId property in [Diagnostic Logs](application-gateway-diagnostics.md#diagnostic-logging).
+X-appgw-trace-id is a unique guid generated by application gateway for each client request and presented in the forwarded request to the backend pool member.  The guid consists of 32 alphanumeric characters presented without dashes (for example: ac882cd65a2712a0fe1289ec2bb6aee7). This guid can be used to correlate a request received by application gateway and initiated to a backend pool member via the transactionId property in [Diagnostic Logs](application-gateway-diagnostics.md#diagnostic-logging).
 
 You can configure application gateway to modify request and response headers and URL by using [Rewrite HTTP headers and URL](rewrite-http-headers-url.md) or to modify the URI path by using a path-override setting. However, unless configured to do so, all incoming requests are proxied to the backend.