Skip to content

Commit 17721e7

Browse files
Incorporate feedback.
1 parent c5aff24 commit 17721e7

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/frontdoor/front-door-faq.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Azure Front Door is an Application Delivery Network (ADN) as a service, offering
2929

3030
### What features does Azure Front Door support?
3131

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).
3333

3434
### What is the difference between Azure Front Door and Azure Application Gateway?
3535

@@ -41,7 +41,7 @@ The key scenarios why one should use Application Gateway behind Front Door are:
4141

4242
- 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.
4343
- 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).
4545
- 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.
4646

4747
### 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
191191

192192
### Does Azure Front Door also support re-encryption of traffic to the backend?
193193

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.
195195

196196
### Does Front Door support self-signed certificates on the backend for HTTPS connection?
197197

articles/frontdoor/front-door-lb-with-azure-app-delivery-suite.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ The following diagram shows the architecture of this scenario:
7373
![Application Delivery Suite Detailed Architecture][2]
7474

7575
> [!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.
7777
7878

7979
## Next Steps

0 commit comments

Comments
 (0)