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: learn-pr/wwl-azure/load-balancing-https-traffic-azure/includes/2-design-azure-application-gateway.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ The [Azure Application Gateway](/azure/application-gateway/overview) processes n
5
5
- A web application firewall (WAF) to protect against web application vulnerabilities.
6
6
- End-to-end request encryption.
7
7
- Autoscaling to dynamically adjust capacity as your web traffic load change.
8
-
- Connection draining allowing graceful removal of back-end pool members during planned service updates.
9
-
- Session stickiness to ensure client requests in the same session are routed to the same back-end server.
8
+
- Connection draining allowing graceful removal of backend pool members during planned service updates.
9
+
- Session stickiness to ensure client requests in the same session are routed to the same backend server.
10
10
- Path and URL based routing.
11
11
12
12
## How Azure Application Gateway works
@@ -16,10 +16,10 @@ The [Azure Application Gateway](/azure/application-gateway/overview) processes n
16
16
Let's review the [Azure Application Gateway components](/azure/application-gateway/application-gateway-components).
17
17
18
18
-**Front-end IP address**. Client requests are received through a front-end IP address. You can configure the Application Gateway to have a public IP address, a private IP address, or both.
19
-
-**Listeners**. A listener is a logical entity that checks for incoming connection requests. A listener accepts a request if the protocol, port, hostname, and IP address match the listeners configuration. You must have at least one listener.
19
+
-**Listeners**. A listener is a logical entity that checks for incoming connection requests. A listener accepts a request if the protocol, port, hostname, and IP address match the listener's configuration. You must have at least one listener.
20
20
-**Request routing rules**. A request routing rule is a key component of an application gateway because it determines how to route traffic on the listener. The rule binds the listener, the backend server pool, and the backend HTTP settings. When a listener accepts a request, the request routing rule forwards the request to the backend or redirects it elsewhere. If the request is forwarded to the backend, the request routing rule defines which backend server pool to forward it to.
21
21
-**Backend pools**. A backend pool is a collection of web servers. Backend targets can include: a fixed set of virtual machines, a virtual machine scale-set, an app hosted by Azure App Services, or a collection of on-premises servers. The backend pool receives and processes requests.
22
-
-**Health probes**. Health probes determine which servers are available for load-balancing in a back-end pool. Servers are automatically added and removed from the backend pool based on their availability.
22
+
-**Health probes**. Health probes determine which servers are available for load-balancing in a backend pool. Servers are automatically added and removed from the backend pool based on their availability.
23
23
24
24
> [!TIP]
25
-
> Learn more about Azure Application Gateway check out the [Introduction to Azure Application Gateway](/training/modules/load-balance-web-traffic-with-application-gateway/) module.
25
+
> Learn more about Azure Application Gateway check out the [Introduction to Azure Application Gateway](/training/modules/intro-to-azure-application-gateway/) module.
Copy file name to clipboardExpand all lines: learn-pr/wwl-azure/load-balancing-https-traffic-azure/includes/3-configure-azure-application-gateway.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,10 @@
1
1
2
2
3
-
This diagram reviews how the Azure Application Gateway components work together.
3
+
This diagram provides more detail on how the Azure Application Gateway components work together.
4
4
5
5
:::image type="content" source="../media/application-gateway-components.png" alt-text="Diagram showing how Azure Application Gateway routes requests to a pool of web servers.":::
6
6
7
+
This video uses the digram to explain how the gateway works.
@@ -12,20 +13,22 @@ This diagram reviews how the Azure Application Gateway components work together.
12
13
13
14
One of the most important gateway configuration settings is the routing rules. The Azure Application Gateway has two primary methods of routing client requests: path-based and multiple sites.
[Path-based routing](/azure/application-gateway/url-route-overview) sends requests with different URL paths to different pools of back-end servers. For example, you could direct video requests to a back-end pool optimized to handle video streaming. You could also direct image requests to a pool of servers that handles image retrieval.
20
19
21
20
:::image type="content" source="../media/path-based-routing.png" alt-text="Diagram that depicts path-based routing in Azure Application Gateway.":::
22
21
23
-
### Multiple site routing
22
+
### Multiple site routings
24
23
25
24
[Multiple site routing](/azure/application-gateway/multiple-site-overview) configures more than one web application on the same Application Gateway instance. In a multiple site configuration, you register multiple DNS names (CNAMEs) for the IP address of the application gateway, specifying the name of each site. Application Gateway uses separate listeners to wait for requests for each site. Each listener passes the request to a different rule, which can route the requests to servers in a different back-end pool. For example, you could direct all requests for `http://contoso.com` to a specific backend pool.
26
25
27
26
:::image type="content" source="../media/multi-site-routing.png" alt-text="Diagram that depicts multi-site routing in Azure Application Gateway.":::
0 commit comments