why is the origin client download so slow

Why is the origin client download so slow how to#
Why is the origin client download so slow code#

Check if the Azure web app is configured with IP-based SSL instead of being SNI based.

The backend pool is an Azure Web Apps server:

EnforceCertificateNameCheck must be disabled.

The returned certificate must match the FQDN.

To resolve this issue, you have two options: The backend server returns a certificate that doesn't match the FQDN of the Azure Front Door backend pool. In the portal, use a toggle button to turn this setting on or off in the Azure Front Door (classic) Design pane.įor Azure Front Door Standard and Premium tier, this setting can be found in the origin settings when you add an origin to an origin group or configuring a route.

Why is the origin client download so slow how to#

How to disable EnforceCertificateNameCheck from the Azure portal: When enabled, Azure Front Door checks that the backend pool host name FQDN matches the backend server certificate's certificate name or one of the entries in the subject alternative names extension.

The backend pool is an Azure Web Apps server.ĮnforceCertificateNameCheck must be disabled.Īzure Front Door has a switch called EnforceCertificateNameCheck.The backend server returns a certificate that doesn't match the FQDN of the Azure Front Door backend pool.The cause of this problem can be one of three things: Going via Azure Front Door results in 503 error responses. Regular requests sent to your backend without going through Azure Front Door are succeeding.Any 503 responses are returned only for Azure Front Door HTTPS-enabled endpoints.The second option is to create a rules set rule to remove Accept-Encoding from the request for byte range requests.ĥ03 responses from Azure Front Door only for HTTPS Symptom The first option is to disable compression on the origin or Azure Front Door. If the client is sending byte range requests with Accept-Encoding headers, you have two options. Using this option leads to the origin responding with different content lengths. If increasing the timeout doesn't resolve the issue, use a tool like Fiddler or your browser's developer tool to check if the client is sending byte range requests with Accept-Encoding headers. Select Origin response timeout and enter a value between 16 and 240 seconds. To configure the setting, go to overview page of the Front Door profile. You can increase the default timeout to up to 4 minutes (240 seconds).

Why is the origin client download so slow code#

If requests going through Azure Front Door result in a 503 error response code then configure the Origin response timeout for Azure Front Door. Create a support request to troubleshoot the issue further. If not, the problem may not be a timeout issue. Send the request through Azure Front Door and see if you're getting any 503 responses. See how long your origin normally takes to respond. Send the request to your origin directly without going through Azure Front Door.

The client sent a byte range request with an Accept-Encoding header, which means compression is enabled.

The time it takes to send a response to the request from Azure Front Door is taking longer than the timeout value.

Your origin is taking longer than the timeout configured to receive the request from Azure Front Door.

The cause of this issue can be one of three things:

Intermittent 503 errors appear with 'ErrorInfo: OriginInvalidResponse.'.

The failure from Azure Front Door typically appears after about 30 seconds.

Going through the Azure Front Door results in 503 or 504 error responses.

503 or 504 response from Azure Front Door after a few seconds Symptom

For more information, see optional response headers. You can request Azure Front Door to return extra debugging HTTP response headers. This article describes how to troubleshoot common routing problems that you might face for your Azure Front Door configuration.