| title | description | documentationcenter | services | author | manager | editor | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create an application gateway by using URL routing rules - Azure CLI 2.0 | Microsoft Docs |
This page provides instructions on how to create and configure an application gateway by using URL routing rules. |
na |
application-gateway |
davidmu1 |
timlt |
tysonn |
application-gateway |
na |
article |
na |
infrastructure-services |
07/26/2017 |
davidmu |
[!div class="op_single_selector"]
With URL path-based routing, you associate routes based on the URL path of HTTP requests. It checks whether there's a route to a back-end server pool configured for the URL listed in the application gateway, and then it sends the network traffic to the defined pool. A common use for URL path-based routing is to load balance requests for different content types to different back-end server pools.
Azure Application Gateway uses two rule types: basic and URL path-based rules. The basic rule type provides round-robin service for the back-end pools. Path-based rules, in addition to round-robin distribution, also use the path pattern of the request URL to choose the appropriate back-end pool.
In the following example, an application gateway serves traffic for contoso.com with two back-end server pools: a default server pool and an image server pool.
Requests for http://contoso.com/image* are routed to the image server pool (imagesBackendPool). If the path pattern doesn't match, the application gateway selects the default server pool (appGatewayBackendPool).
Open the Microsoft Azure Command Prompt and sign in:
az login -u "username"
Note
You can also use az login without the switch for device login that requires entering a code at aka.ms/devicelogin.
After you enter the preceding command, you receive a code. Go to https://aka.ms/devicelogin in a browser to continue the sign-in process.
In the browser, enter the code you received. This redirects you to a sign-in page.
Enter the code to sign in, and then close the browser to continue.
The following steps show you how to add a path-based rule to an existing application gateway.
Configure the application gateway setting imagesBackendPool for the load-balanced network traffic in the back-end pool. In this example, you configure different back-end pool settings for the new back-end pool. Each back-end pool can have its own setting. Path-based rules use back-end HTTP settings to route traffic to the correct back-end pool members. This determines the protocol and port that's used when sending traffic to the back-end pool members. The back-end HTTP settings also determine cookie-based sessions. If enabled, cookie-based session affinity sends traffic to the same back end as previous requests for each packet.
az network application-gateway address-pool create \
--gateway-name AdatumAppGateway \
--name imagesBackendPool \
--resource-group myresourcegroup \
--servers 10.0.0.6 10.0.0.7
The front-end port configuration object is used by a listener to define what port the application gateway listens for traffic on the listener.
az network application-gateway frontend-port create --port 82 --gateway-name AdatumAppGateway --resource-group myresourcegroup --name port82
This step configures the listener for the public IP address and port used to receive incoming network traffic. The following example takes the previously configured front-end IP configuration, front-end port configuration, and a protocol (http or https, which are case sensitive) and configures the listener. In this example, the listener listens to HTTP traffic on port 82 on the public IP address created earlier in this scenario.
az network application-gateway http-listener create --name imageListener --frontend-ip appGatewayFrontendIP --frontend-port port82 --resource-group myresourcegroup --gateway-name AdatumAppGateway
This step configures the relative URL path used by the application gateway to define the mapping between the path and the back-end pool assigned to handle the incoming traffic.
Important
Each path must start with "/", and the only place an asterisk is allowed is at the end. Valid examples are /xyz, /xyz* or /xyz/*. The string fed to the path matcher does not include any text after the first "?" or "#", and those characters are not allowed.
The following example creates one rule for the /images/* path, routing traffic to the back-end imagesBackendPool. This rule ensures that traffic for each set of URLs is routed to the back end. For example, http://adatum.com/images/figure1.jpg goes to imagesBackendPool. If the path doesn't match any of the pre-defined path rules, the rule path map configuration also configures a default back-end address pool. For example, http://adatum.com/shoppingcart/test.html goes to pool1 because it is defined as the default pool for unmatched traffic.
az network application-gateway url-path-map create \
--gateway-name AdatumAppGateway \
--name imagespathmap \
--paths /images/* \
--resource-group myresourcegroup2 \
--address-pool imagesBackendPool \
--default-address-pool appGatewayBackendPool \
--default-http-settings appGatewayBackendHttpSettings \
--http-settings appGatewayBackendHttpSettings \
--rule-name images
If you want to learn about Secure Sockets Layer (SSL) offload, see Configure an application gateway for SSL offload.