增加 110 秒的请求超时
Increasing request timeout of 110s
我似乎无法将请求的 110 秒超时延长到我的 Azure Web 应用程序。为了增加此限制，我做了以下操作，但没有成功。
ASP.NET的HTTP请求执行超时（web.config）：
<system.web>
<httpRuntime executionTimeout="600" />
</system.web>
IIS 连接超时（web.config）：
<system.applicationHost>
<webLimits connectionTimeout="00:10:00" />
</system.applicationHost>
杀死外部命令前的 Kudu 超时（站点应用程序设置）：
SCM_COMMAND_IDLE_TIMEOUT = 600
我错过了什么？
request timeout of 110s
很奇怪你的请求超时110s，来自Auzre official document, we could know that default timeout is about 4 minutes.It seems that we are not able to increase request timeout. The following is the snippet from the document. Please have a try to scale up and scale down back the App service plan。如果仍然有同样的问题，请联系 Azure 支持团队以获得更多帮助。
Azure Load Balancer has a default idle timeout setting of four minutes. This is generally a reasonable response time limit for a web request. If your web app requires background processing, we recommend using Azure WebJobs. The Azure web app can call WebJobs and be notified when background processing is finished. You can choose from multiple methods for using WebJobs, including queues and triggers.
+
WebJobs is designed for background processing. You can do as much background processing as you want in a WebJob. For more information about WebJobs, see Run background tasks with WebJobs.
注意 :SCM_COMMAND_IDLE_TIMEOUT = 600 可以用于您的构建过程在服务器端启动一些命令。但是请求超时会导致客户端在 230 秒后断开连接，我们可以从 Azure Kudu Configurable settings.
获得更多信息
我似乎无法将请求的 110 秒超时延长到我的 Azure Web 应用程序。为了增加此限制，我做了以下操作，但没有成功。
ASP.NET的HTTP请求执行超时（web.config）：
<system.web>
<httpRuntime executionTimeout="600" />
</system.web>
IIS 连接超时（web.config）：
<system.applicationHost>
<webLimits connectionTimeout="00:10:00" />
</system.applicationHost>
杀死外部命令前的 Kudu 超时（站点应用程序设置）：
SCM_COMMAND_IDLE_TIMEOUT = 600
我错过了什么？
request timeout of 110s
很奇怪你的请求超时110s，来自Auzre official document, we could know that default timeout is about 4 minutes.It seems that we are not able to increase request timeout. The following is the snippet from the document. Please have a try to scale up and scale down back the App service plan。如果仍然有同样的问题，请联系 Azure 支持团队以获得更多帮助。
Azure Load Balancer has a default idle timeout setting of four minutes. This is generally a reasonable response time limit for a web request. If your web app requires background processing, we recommend using Azure WebJobs. The Azure web app can call WebJobs and be notified when background processing is finished. You can choose from multiple methods for using WebJobs, including queues and triggers. + WebJobs is designed for background processing. You can do as much background processing as you want in a WebJob. For more information about WebJobs, see Run background tasks with WebJobs.
注意 :SCM_COMMAND_IDLE_TIMEOUT = 600 可以用于您的构建过程在服务器端启动一些命令。但是请求超时会导致客户端在 230 秒后断开连接，我们可以从 Azure Kudu Configurable settings.