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/frontdoor/front-door-faq.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Azure Front Door is an Application Delivery Network (ADN) as a service, offering
29
29
30
30
### What features does Azure Front Door support?
31
31
32
-
Azure Front Door supports dynamic site acceleration (DSA), TLS offloading and end to end TLS, Web Application Firewall, cookie-based session affinity, url path-based routing, free certificates and multiple domain management, and others. For a full list of supported features, see [Overview of Azure Front Door](front-door-overview.md).
32
+
Azure Front Door supports dynamic site acceleration (DSA), TLS/SSL offloading and end to end TLS, Web Application Firewall, cookie-based session affinity, url path-based routing, free certificates and multiple domain management, and others. For a full list of supported features, see [Overview of Azure Front Door](front-door-overview.md).
33
33
34
34
### What is the difference between Azure Front Door and Azure Application Gateway?
35
35
@@ -41,7 +41,7 @@ The key scenarios why one should use Application Gateway behind Front Door are:
41
41
42
42
- Front Door can perform path-based load balancing only at the global level but if one wants to load balance traffic even further within their virtual network (VNET) then they should use Application Gateway.
43
43
- Since Front Door doesn't work at a VM/container level, so it cannot do Connection Draining. However, Application Gateway allows you to do Connection Draining.
44
-
- With an Application Gateway behind AFD, one can achieve 100% TLS offload and route only HTTP requests within their virtual network (VNET).
44
+
- With an Application Gateway behind AFD, one can achieve 100% TLS/SSL offload and route only HTTP requests within their virtual network (VNET).
45
45
- Front Door and Application Gateway both support session affinity. While Front Door can direct subsequent traffic from a user session to the same cluster or backend in a given region, Application Gateway can direct affinitize the traffic to the same server within the cluster.
46
46
47
47
### Can we deploy Azure Load Balancer behind Front Door?
@@ -191,7 +191,7 @@ Yes, OCSP stapling is supported by default by Front Door and no configuration is
191
191
192
192
### Does Azure Front Door also support re-encryption of traffic to the backend?
193
193
194
-
Yes, Azure Front Door supports TLS offload, and end to end TLS, which re-encrypts the traffic to the backend. In fact, since the connections to the backend happen over it's public IP, it is recommended that you configure your Front Door to use HTTPS as the forwarding protocol.
194
+
Yes, Azure Front Door supports TLS/SSL offload, and end to end TLS, which re-encrypts the traffic to the backend. In fact, since the connections to the backend happen over it's public IP, it is recommended that you configure your Front Door to use HTTPS as the forwarding protocol.
195
195
196
196
### Does Front Door support self-signed certificates on the backend for HTTPS connection?
Copy file name to clipboardExpand all lines: articles/frontdoor/front-door-lb-with-azure-app-delivery-suite.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ The following diagram shows the architecture of this scenario:
73
73
![Application Delivery Suite Detailed Architecture][2]
74
74
75
75
> [!NOTE]
76
-
> This example is only one of many possible configurations of the load-balancing services that Azure offers. Traffic Manager, Front Door, Application Gateway, and Load Balancer can be mixed and matched to best suit your load-balancing needs. For example, if TLS offload or Layer 7 processing is not necessary, Load Balancer can be used in place of Application Gateway.
76
+
> This example is only one of many possible configurations of the load-balancing services that Azure offers. Traffic Manager, Front Door, Application Gateway, and Load Balancer can be mixed and matched to best suit your load-balancing needs. For example, if TLS/SSL offload or Layer 7 processing is not necessary, Load Balancer can be used in place of Application Gateway.
0 commit comments