Skip to content

Commit 8447044

Browse files
authored
Merge pull request #193798 from JackStromberg/patch-50
Consistency per customer feedback
2 parents d380b3f + 4c22611 commit 8447044

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/ssl-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ In this example, requests using TLS1.2 are routed to backend servers in Pool1 us
7777

7878
## End to end TLS and allow listing of certificates
7979

80-
Application Gateway only communicates with known backend instances that have allow listed their certificate with the application gateway. There are some differences in the end-to-end TLS setup process with respect to the version of Application Gateway used. The following section explains them individually.
80+
Application Gateway only communicates with those backend servers that have either allow listed their certificate with the Application Gateway or whose certificates are signed by well-known CA authorities and the certificate's CN matches the host name in the HTTP backend settings. There are some differences in the end-to-end TLS setup process with respect to the version of Application Gateway used. The following section explains them individually.
8181

8282
## End-to-end TLS with the v1 SKU
8383

0 commit comments

Comments
 (0)