10000 | “%1”: 值不能为空。 |
'%1': Value must not be empty. |
10001 | “%1”: 缓冲区空间不足,无法容纳请求的字节数。 |
'%1': Buffer does not have enough space to hold the requested number of bytes. |
10002 | “%1”: 发现无效字符。 |
'%1': Invalid characters found. |
10003 | 无效的 HTTP 标头。 |
Invalid HTTP headers. |
10004 | 无效的 HTTP 响应状态。 |
Invalid HTTP response status. |
10005 | “%1”: 提供的值不是可忽略的 ChainValidationResult 值。 |
'%1': Provided value is not an ignorable ChainValidationResult value. |
31000 | 这个实例已经发出了一个或多个请求。属性只能在发送第一个请求之前进行修改。 |
This instance has already started one or more requests. Properties can only be modified before sending the first request. |
31001 | 已发送请求消息。无法多次发送相同的请求消息。 |
The request message was already sent. Cannot send the same request message multiple times. |
31002 | 提供的请求 URI 无效。 |
An invalid request URI was provided. |
31003 | 误用的标头名称。请确保将请求标头与 HttpRequestMessage 配合使用,将响应标头与 HttpResponseMessage 配合使用,将内容标头与 HttpContent 对象配合使用。 |
Misused header name. Make sure request headers are used with HttpRequestMessage, response headers with HttpResponseMessage, and content headers with HttpContent objects. |
31004 | 响应状态代码未指示成功: %1!u! (%2!s!)。 |
Response status code does not indicate success: %1!u! (%2!s!). |
31005 | 指定的证书缺少所需的私钥信息。 |
The certificate specified is missing the required private key information. |
31006 | “传输编码: 区块”标头不能与无内容的对象一同使用。 |
'Transfer-Encoding: chunked' header cannot be used with no content object. |
31007 | 不能同时指定“内容长度”和“传输编码: 区块”标头。 |
Both 'Content-Length' and 'Transfer-Encoding: chunked' headers can not be specified at the same time. |
31008 | 正在发送一个支持 ControlChannelTrigger,并且要求一个只使用 HttpBaseProtocolFilter 的筛选器管道的 HttpRequestMessage。 |
Sending an HttpRequestMessage that is ControlChannelTrigger enabled requires a filter pipeline that uses only HttpBaseProtocolFilter. |
31009 | HttpMultipartContent 需要至少有一个部件。 |
HttpMultipartContent requires there to be at least one part. |
31010 | 无法修改缓冲后的 HttpMultipartContent。 |
Cannot modify HttpMultipartContent after it has already been buffered. |
31011 | 内容长度大于 UINT32_MAX。使用“传输编码: 区块”替代。 |
Content-Length greater than UINT32_MAX. Use 'Transfer-Encoding: chunked' instead. |
31012 | IHttpContent 流需要多次写入,但不能多次读取。在调用此方法之前,请使用 IRandomAccessStream 支持的 IHttpContent,或调用 BufferAllAsync。 |
The IHttpContent stream needed to be written multiple times, but could not be read multiple times. Use an IHttpContent backed by an IRandomAccessStream or call BufferAllAsync before calling this method. |
0x30000000 | 信息 |
Info |
0x50000002 | 错误 |
Error |
0x50000003 | 警告 |
Warning |
0x50000005 | 详细 |
Verbose |
0x70000001 | Http 异步 I/O |
Http Async I/O |
0x70000002 | Http 操作 |
Http Operation |
0x70000003 | Http Cct |
Http Cct |
0x90000001 | Microsoft-Windows-Runtime-Web-Http |
Microsoft-Windows-Runtime-Web-Http |
0xB0000001 | 无法分析 URI“%1”。 |
Failed to parse URI '%1'. |
0xB0000002 | 无法使用基本 URI“%1”和相对 URI“%2”创建 URI。 |
Failed to create URI with base URI '%1' and relative URI '%2'. |
0xB0000003 | 添加 HTTP 标头“%1: %2”。 |
Add HTTP header '%1: %2'. |
0xB0000004 | 开始使用凭据“%2”连接到“%1”。 |
Start to connect to '%1' with credential of '%2'. |
0xB0000005 | 开始使用默认凭据连接到“%1”。 |
Start to connect to '%1' with default credential. |
0xB0000006 | 无法在端口 %2 上连接到“%1”。最后一个错误为 %3: %4 |
Failed to connect to '%1' at port %2. The last error is %3: %4 |
0xB0000007 | 正在使用标志 %3 将对“%1”的请求打开到“%2”。 |
Opening request to '%1' to '%2' with flags %3. |
0xB0000008 | 无法打开对“%1”的请求。最后一个错误为 %2: %3 |
Failed to open request to '%1'. The last error is %2: %3 |
0xB0000009 | 请求上下文 %1 具有到“%3”的请求句柄 %2。 |
Request context %1 has request handle %2 to '%3'. |
0xB000000A | 将请求句柄 %1 上的 HTTP 发送和接收超时设置为 %2 毫秒。 |
Set HTTP send and receive timeout to %2ms on request handle %1. |
0xB000000B | 开始发送到内容长度为 %2 的请求句柄 %1。 |
Start to send to request handle %1 with content length %2. |
0xB000000C | 请求句柄 %1 已同步完成。 |
Request handle %1 completed synchronously. |
0xB000000D | 请求上下文 %1 已完成异步发送。 |
Request context %1 completed send asynchronously. |
0xB000000E | 正在向请求句柄 %1 写入 %2 个字节。 |
Writing %2 bytes to request handle %1. |
0xB000000F | 无法将实体正文发送到请求句柄 %1。最后一个错误为 %2: %3 |
Failed to send entity body to request handle %1. The last error is %2: %3 |
0xB0000010 | 已在请求句柄 %1 上发送 HTTP 请求: %2 |
Sent HTTP request at request handle %1: %2 |
0xB0000011 | 开始接收来自请求句柄 %1 的响应。 |
Start to receive response from request handle %1. |
0xB0000012 | 已接收来自请求句柄 %1 的 HTTP 响应,状态代码为 %2,状态描述为“%3”。 |
Received HTTP response from request handle %1 with status code %2 and status description '%3'. |
0xB0000013 | 接收来自请求句柄 %1 的 HTTP 响应: %2 |
Receive HTTP response from request handle %1: %2 |
0xB0000014 | 无法接收来自请求句柄 %1 的 HTTP 响应。最后一个错误为 %2: %3 |
Failed to receive HTTP response from request handle %1. The last error is %2: %3 |
0xB0000015 | 请求上下文 %1 已接收到 %2 个字节的 HTTP 响应,超过了 %3 的限制。 |
Request context %1 received HTTP response of %2 bytes, which is over the %3 limit. |
0xB0000016 | 请求上下文 %1 正在重新提交请求。 |
Request context %1 resubmitting the request. |
0xB0000017 | 正在为服务器“%2”重用请求句柄 %1。 |
Reusing the request handle %1 for server '%2'. |
0xB0000018 | 请求上下文 %1 已中止。 |
Request context %1 was aborted. |
0xB0000019 | “%1”的进度: %2 阶段,%3 次重试,已发送 %4 个字节;要发送的字节总数为 %5;已接收 %6 个字节;要接收的字节总数为 %7。 |
Progress to '%1': %2 stage; %3 retries; %4 bytes sent; %5 total bytes to send; %6 bytes received; %7 total bytes to receive. |
0xB000001A | 已完成对“%1”的 HTTP 请求。错误代码为 %2: %3 |
HTTP request to '%1' completed. The error code is %2: %3 |
0xB000001B | %2 上的异步操作 %1 无法处理 HTTP 响应“%3”。错误代码为 %4: %5 |
Async operation %1 at %2 failed to process HTTP response '%3'. The error code is %4: %5 |
0xB000001C | %2 上的异步操作 %1 已开始。 |
Async operation %1 at %2 started. |
0xB000001D | %2 上的异步操作 %1 无法开始。错误代码为 %3: %4 |
Async operation %1 at %2 failed to start. The error code is %3: %4 |
0xB000001E | %2 上的异步操作 %1 已成功完成。 |
Async operation %1 at %2 completed successfully. |
0xB000001F | %2 上的异步操作 %1 失败,错误代码为 %3: %4 |
Async operation %1 at %2 failed with error code %3: %4 |
0xB0000020 | %2 上的异步操作 %1 已取消。 |
Async operation %1 at %2 was canceled. |
0xB0000021 | %2 上的异步操作 %1 已关闭。 |
Async operation %1 at %2 was closed. |
0xB0000022 | %2 上的异步操作 %1 已调用进度委托。 |
Async operation %1 at %2 called progress delegate. |
0xB0000023 | 响应状态为 %1 的 CompleteDelivery 循环;%2 个挂起的接收操作。 |
CompleteDelivery loop with %1 response state; %2 pending receive operations. |
0xB0000024 | CompleteDelivery 进入。 |
CompleteDelivery enter. |
0xB0000025 | CompleteDelivery 退出,%1 为 %2 |
CompleteDelivery exit with %1: %2 |
0xB0000026 | 刷新进入。 |
Flush enter. |
0xB0000027 | 刷新退出,%1 为 %2 |
Flush exit with %1: %2 |
0xB0000028 | 将挂起的接收操作减少为 %1。 |
Decrement pending receive operations to %1. |
0xB0000029 | 将挂起的接收操作增加为 %1。 |
Increment pending receive operations to %1. |
0xB000002A | 将响应状态设为 %1。 |
Set response state to %1. |
0xB000002B | 句柄 %1: HTTP/2 已启用。 |
Handle %1: HTTP/2 enabled. |
0xB000002C | 在 %2 上执行的异步操作 %1 已启动服务器自定义验证。 |
Async operation %1 at %2 started server custom validation. |
0xB000002D | 在 %2 上执行的异步操作 %1 正在等待服务器自定义验证完成。 |
Async operation %1 at %2 waiting for completion of server custom validation. |
0xB000002E | 在 %2 上执行的异步操作 %1 未通过服务器自定义验证。 |
Async operation %1 at %2 failed server custom validation. |
0xB000002F | 在 %2 上执行的异步操作 %1 成功完成服务器自定义验证。 |
Async operation %1 at %2 successfully completed server custom validation. |
0xB0000030 | 由于父窗口句柄无法确定,无法显示对话框。 |
A dialog cannot be displayed because the parent window handle cannot be determined. |
0xD0000001 | BufferAllOperation |
BufferAllOperation |
0xD0000002 | BufferResponseOperation |
BufferResponseOperation |
0xD0000003 | MultipartBufferAllOperation |
MultipartBufferAllOperation |
0xD0000004 | MultipartWriteToStreamOperation |
MultipartWriteToStreamOperation |
0xD0000005 | ReadAsBufferOperation |
ReadAsBufferOperation |
0xD0000006 | ReadAsStreamOperation |
ReadAsStreamOperation |
0xD0000007 | ReadAsStringOperation |
ReadAsStringOperation |
0xD0000008 | SendRequestOperation |
SendRequestOperation |
0xD0000009 | WriteToStreamOperation |
WriteToStreamOperation |
0xD000000A | None |
None |
0xD000000B | DetectingProxy |
DetectingProxy |
0xD000000C | ResolvingName |
ResolvingName |
0xD000000D | ConnectingToServer |
ConnectingToServer |
0xD000000E | NegotiatingSsl |
NegotiatingSsl |
0xD000000F | SendingHeaders |
SendingHeaders |
0xD0000010 | SendingContent |
SendingContent |
0xD0000011 | WaitingForResponse |
WaitingForResponse |
0xD0000012 | ReceivingHeaders |
ReceivingHeaders |
0xD0000013 | ReceivingContent |
ReceivingContent |
0xD0000014 | IncompleteAndReceiving |
IncompleteAndReceiving |
0xD0000015 | IncompleteAndPending |
IncompleteAndPending |
0xD0000016 | 完成 |
Complete |