Skip to content

Commit b094f76

Browse files
Update edgio-retirement-faq.md
1 parent 0de0db7 commit b094f76

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cdn/edgio-retirement-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Important notes regarding these "best effort" automatic migrations to Azure Fron
6464
| Customer was using SAS token through rule engine to access their Azure Storage backend which has public access disabled | [Upgrade](../frontdoor/tier-upgrade.md) to Front Door Premium and use [private link](../frontdoor/standard-premium/how-to-enable-private-link-storage-account.md). If you're facing any errors in setting up private link, raise a support ticket. |
6565
| Customer was using geo-filtering rules which weren't migrated | [Configure geo-filtering using WAF](../web-application-firewall/afds/waf-front-door-tutorial-geo-filtering.md)|
6666
| Customer sees 502 Bad Gateway error | This happens when the hostname in origin certificate doesn't match the origin hostname/host header. To mitigate [disable 'Certificate subject name validation'](../frontdoor/how-to-configure-origin.md) at the origin. |
67-
| Customers were using [CORS on Edgio](cdn-cors.md) and is seeing their traffic blocked on AFD | No mitigation available as [domain fronting behavior is blocked on AFD](https://techcommunity.microsoft.com/blog/azurenetworkingblog/prohibiting-domain-fronting-with-azure-front-door-and-azure-cdn-standard-from-mi/4006619). No exceptions are possible. |
67+
| Customer is exhibiting domain fronting behaviour as the host header and SNI are different | Include the two domains in the routes/routing rules and select HTTP and HTTPS or HTTPS as the Accepted Protocol in the routes/routing rules. [More details here.](https://techcommunity.microsoft.com/blog/azurenetworkingblog/prohibiting-domain-fronting-with-azure-front-door-and-azure-cdn-standard-from-mi/4006619). |
6868
| Customer was using self signed certificates | Use Front Door [managed certificates](../frontdoor/standard-premium/how-to-configure-https-custom-domain.md) or create a complete certificate chain with an allowed Certificate Authority (CA) that is part of the [Microsoft Trusted CA List](https://ccadb.my.salesforce-sites.com/microsoft/IncludedCACertificateReportForMSFT). If you use a non-allowed CA, your request will be rejected. |
6969

7070
Certificates from internal CAs or self-signed certificates aren't allowed.

0 commit comments

Comments
 (0)