大网数据广告活动
Web服务器与PHP

Server Timeouts Property

· 52CE 我爱测

The HTTP Server API enables applications to set the server connection timeout limits on a server session or a URL group. The HTTP timeouts property is used to set all timeouts on an application-specific basis. The IdleConnection and HeaderWait timers can also be configured HTTP Server API-wide. When the timers are configured HTTP Server API-wide, they…

The HTTP Server API enables applications to set the server connection timeout limits on a server session or a URL group. The HTTP timeouts property is used to set all timeouts on an application-specific basis. The IdleConnection and HeaderWait timers can also be configured HTTP Server API-wide. When the timers are configured HTTP Server API-wide, they apply to all the HTTP Server API applications on the computer and the settings persist when the service is restarted.

For more information about configuring timers, see Configuring the Application Specific Timeouts.

When the timers are not configured for a URL group or server session, the HTTP Server API default configurations apply.

The order of timeout enforcement is as follows:

  1. The HTTP Server API-wide defaults apply to all the HTTP Server API applications on the computer.
  2. The Server Session timeouts override the HTTP Server API-wide settings, when set.
  3. The URL group settings override the server session configurations, when set.

The following table lists the default connection timeout limits

Timer Definition HTTP Server API default Configurable as HTTP Server API wide Configurable as Application specific
IdleConnection The connection expired while staying idle. 120 Sec Yes Limited
HeaderWait The connection expired while waiting for the HTTP Server API to parse the header. 120 Sec Yes Limited
EntityBody The connection expired while waiting for the request entity body to arrive. 120 Sec No Yes
DrainEntityBody The connection expired while waiting for the HTTP Server API to drain the entity body on a Keep-Alive connection. 120 Sec No Yes
MinSendRate The connection expired because the response send rate was slower than the default of 150 bytes/sec. 150 Sec No Yes
RequestQueue The connection expired because the request remained in the request queue before the application picked it up. 120 Bytes/Sec No Yes

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。