最新
活动
咨询
购物车
帮助
重要通知

HTTPERR错误说明

  • 作者:
  • 文章来源:
  • 更新时间:2015-03-16 15:38:16

 

原因短语

说明

AppOffline

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为应用程序错误导致应用程序脱机。

AppPoolTimer

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为应用程序池过程太忙,无法处理请求。

AppShutdown

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为该应用程序关闭自动以管理员策略响应。

BadRequest

处理请求时出现分析错误。

Connection_Abandoned_By_AppPool

从该应用程序池工作进程已意外退出或关闭其句柄的孤立待定的请求。

Connection_Abandoned_By_ReqQueue

从该应用程序池工作进程已意外退出或关闭其句柄的孤立待定的请求。特定于 Windows Vista Windows Server 2008

Connection_Dropped

服务器可以发送其最终的响应数据包之前,客户端和服务器之间连接被关闭。此行为的最常见的原因是客户端过早关闭其连接到服务器。

Connection_Dropped_List_Full

被删除客户端和服务器之间的连接的列表已满。特定于 Windows Vista Windows Server 2008

ConnLimit

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为已达到或超过了在站点级别的连接限制。

Connections_Refused

内核非页面池(NonPagedPool 内存已少于 20 MB http.sys 已停止接收新的连接

Disabled

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为管理员已脱机应用程序。

EntityTooLarge

实体超出所允许的最大大小。

FieldLength

超出了字段长度限制。

Forbidden

分析时遇到了一个被禁止的元素或序列。

Header

在标题中出现分析错误。

Hostname

处理一个主机名时出现分析错误。

Internal

发生了内部服务器错误 (HTTP 错误 500)。

Invalid_CR/lf

发生一个非法回车或换行。

LengthRequired

缺少所需的长度值。

N/A

服务不可用时出错 HTTP 错误 503)。由于出现内部错误 (如内存分配故障),该服务不可用。

N / i

一个不实现时,出现了错误 (HTTP 错误 501),或服务不可用错误 (HTTP 错误 503 由于未知的传输编码。

Number

处理数字时出现分析错误。

Precondition

缺少所需的前提条件。

QueueFull

出现服务不可用错误 (HTTP 错误 503)。该服务不可用,因为应用程序请求队列已满。

RequestLength

超出了请求长度限制。

Timer_AppPool

连接因为在程序池队列中到期请求等候处理的时间太长已过期,此超时持续时间为 连接超时。默认状态下,此值设置为两分钟。

Timer_ConnectionIdle

连接已过期,并保持空闲。默认 连接超时 持续时间为两分钟。

Timer_EntityBody

连接过期之前到达请求实体正文。当清除一个请求有一个实体正文 HTTP API 打开 Timer_EntityBody 计时器。最初,此计时器的限制设置为 连接超时 (通常为 2 分钟)。在此的请求接收到另一种数据表示每次 HTTP API 重置计时器赋予连接两分钟 (或在 $ ConnectionTimeout 中指定的任何内容)。

Timer_HeaderWait

连接已过期因为标头分析请求所花费更多的时间超过两分钟的默认限制。

Timer_MinBytesPerSecond

连接已过期因为客户端不接收响应以合理的速度。响应发送率不低于 240 字节/秒的默认值。

Timer_ReqQueue

连接已过期因为请求等待在应用程序池队列的服务器应用程序将出列时间太长。此超时持续时间为 连接超时。默认状态下,此值设置为两分钟。特定于 Windows Vista Windows Server 2008

Timer_Response

保留。当前未使用。

URL

处理 URL 时出现分析错误。

URL_Length

URL 超过了允许大小的最大值。

Verb

处理谓词时出现分析错误。

Version_N/s

在版本不支持时出错 HTTP 错误 505)。

 

 

 

 

Reason Phrase

Description

AppOffline

A service unavailable error occurred (an HTTP error 503). The service is not available because application errors caused the application to be taken offline.

AppPoolTimer

A service unavailable error occurred (an HTTP error 503). The service is not available because the application pool process is too busy to handle the request.

AppShutdown

A service unavailable error occurred (an HTTP error 503). The service is not available because the application shut down automatically in response to administrator policy.

BadRequest

A parse error occurred while processing a request.

Connection_Abandoned_By_AppPool

A worker process from the application pool has quit unexpectedly or orphaned a pending request by closing its handle.

Connection_Abandoned_By_ReqQueue

A worker process from the application pool has quit unexpectedly or orphaned a pending request by closing its handle. Specific to Windows Vista and Windows Server 2008.

Connection_Dropped

The connection between the client and the server was closed before the server could send its final response packet. The most common cause of this behavior is that the client prematurely closes its connection to the server.

Connection_Dropped_List_Full

The list of dropped connections between clients and the server is full. Specific to Windows Vista and Windows Server 2008.

ConnLimit

A service unavailable error occurred (an HTTP error 503). The service is not available because the site level connection limit has been reached or exceeded.

Connections_Refused

The kernel NonPagedPool memory has dropped below 20MB and http.sys has stopped receiving new connections

Disabled

A service unavailable error occurred (an HTTP error 503). The service is not available because an administrator has taken the application offline.

EntityTooLarge

An entity exceeded the maximum size that is permitted.

FieldLength

A field length limit was exceeded.

Forbidden

A forbidden element or sequence was encountered while parsing.

Header

A parse error occurred in a header.

Hostname

A parse error occurred while processing a Hostname.

Internal

An internal server error occurred (an HTTP error 500).

Invalid_CR/LF

An illegal carriage return or line feed occurred.

LengthRequired

A required length value was missing.

N/A

A service unavailable error occurred (an HTTP error 503). The service is not available because an internal error (such as a memory allocation failure) occurred.

N/I

A not-implemented error occurred (an HTTP error 501), or a service unavailable error occurred (an HTTP error 503) because of an unknown transfer encoding.

Number

A parse error occurred while processing a number.

Precondition

A required precondition was missing.

QueueFull

A service unavailable error occurred (an HTTP error 503). The service is not available because the application request queue is full.

RequestLength

A request length limit was exceeded.

Timer_AppPool

The connection expired because a request waited too long in an application pool queue for a server application to dequeue and process it. This timeout duration is ConnectionTimeout. By default, this value is set to two minutes.

Timer_ConnectionIdle

The connection expired and remains idle. The default ConnectionTimeout duration is two minutes.

Timer_EntityBody

The connection expired before the request entity body arrived. When it is clear that a request has an entity body, the HTTP API turns on the Timer_EntityBody timer. Initially, the limit of this timer is set to the ConnectionTimeout value (typically 2 minutes). Each time another data indication is received on this request, the HTTP API resets the timer to give the connection two more minutes (or whatever is specified in ConnectionTimeout).

Timer_HeaderWait

The connection expired because the header parsing for a request took more time than the default limit of two minutes.

Timer_MinBytesPerSecond

The connection expired because the client was not receiving a response at a reasonable speed. The response send rate was slower than the default of 240 bytes/sec.

Timer_ReqQueue

The connection expired because a request waited too long in an application pool queue for a server application to dequeue. This timeout duration is ConnectionTimeout. By default, this value is set to two minutes. Specific to Windows Vista and Windows Server 2008.

Timer_Response

Reserved. Not currently used.

URL

A parse error occurred while processing a URL.

URL_Length

A URL exceeded the maximum permitted size.

Verb

A parse error occurred while processing a verb.

Version_N/S

A version-not-supported error occurred (an HTTP error 505).

 

 

注册表值

说明

EnableErrorLogging

DWORD 您可以设置为 TRUE 来启用错误日志记录或 FALSE 禁用它。默认值为 TRUE

ErrorLogFileTruncateSize

一个 dword ,指定一个错误日志文件的最大大小以字节为单位)。 默认值为 1 MB 0x100000)。

注意指定的值不能小于默认值。

ErrorLoggingDir

一个 字符串,用于指定 HTTP API 将其日志记录的文件放入该文件夹。

HTTP API
中指定的文件夹中创建子文件夹 HTTPERR,然后将日志文件存储在子文件夹。 此子文件夹和日志文件收到相同的权限设置。在管理员和本地系统帐户拥有完全访问权限。其他用户不具有访问权限。

以下是在注册表中未指定该文件夹时的默认文件夹:
%SystemRoot%\System32\LogFiles

注意ErrorLoggingDir 字符串值必须是完全限定的路径。但是,它可以包含 %systemroot%

 

FTP

增值电信业务经营许可证:B1-20140435 京B2-20070152 域名注册服务批文号:信部电函[2005]263号 京ICP证000012
 京公网安备11030102000056号 京ICP备09061941号-4
Copyright©1993-2018 北京新网数码信息技术有限公司 版权所有