Microsoft-Windows-Runtime-Web-Http

48 events across 1 channel

Event ID	Title	Channel
1	Failed to parse URI '.	Tracing
2	Failed to create URI with base URI '.	Tracing
3	Add HTTP header '.	Tracing
4	Start to connect to '.	Tracing
5	Start to connect to '.	Tracing
6	Failed to connect to '.	Tracing
7	Opening request to '.	Tracing
8	Failed to open request to '.	Tracing
9	Request context %1 has request handle %2 to '%3'.	Tracing
10	Set HTTP send and receive timeout to %2ms on request handle %1.	Tracing
11	Start to send to request handle %1 with content length %2.	Tracing
12	Request handle %1 completed synchronously.	Tracing
13	Request context %1 completed send asynchronously.	Tracing
14	Writing %2 bytes to request handle %1.	Tracing
15	Failed to send entity body to request handle %1.	Tracing
16	Sent HTTP request at request handle %1: %2.	Tracing
17	Start to receive response from request handle %1.	Tracing
18	Received HTTP response from request handle %1 with status code %2 and status …	Tracing
19	Receive HTTP response from request handle %1: %2.	Tracing
20	Failed to receive HTTP response from request handle %1.	Tracing
21	Request context %1 received HTTP response of %2 bytes, which is over the %3 …	Tracing
22	Request context %1 resubmitting the request.	Tracing
23	Reusing the request handle %1 for server '%2'.	Tracing
24	Request context %1 was aborted.	Tracing
25	Progress to '.	Tracing
26	HTTP request to '.	Tracing
27	Async operation %1 at %2 failed to process HTTP response '%3'.	Tracing
28	Async operation %1 at %2 started.	Tracing
29	Async operation %1 at %2 failed to start.	Tracing
30	Async operation %1 at %2 completed successfully.	Tracing
31	Async operation %1 at %2 failed with error code %3: %4.	Tracing
32	Async operation %1 at %2 was canceled.	Tracing
33	Async operation %1 at %2 was closed.	Tracing
34	Async operation %1 at %2 called progress delegate.	Tracing
35	CompleteDelivery loop with %1 response state; %2 pending receive operations.	Tracing
36	CompleteDelivery enter.	Tracing
37	CompleteDelivery exit with %1: %2.	Tracing
38	Flush enter.	Tracing
39	Flush exit with %1: %2.	Tracing
40	Decrement pending receive operations to %1.	Tracing
41	Increment pending receive operations to %1.	Tracing
42	Set response state to %1.	Tracing
43	Handle %1: HTTP/2 enabled.	Tracing
44	Async operation %1 at %2 started server custom validation.	Tracing
45	Async operation %1 at %2 waiting for completion of server custom validation.	Tracing
46	Async operation %1 at %2 failed server custom validation.	Tracing
47	Async operation %1 at %2 successfully completed server custom validation.	Tracing
48	A dialog cannot be displayed because the parent window handle cannot be …	Tracing

Event ID 1 — Failed to parse URI '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to parse URI '%1'.

Fields

Name	Description
`uri`	—

Event ID 2 — Failed to create URI with base URI '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to create URI with base URI '%1' and relative URI '%2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 3 — Add HTTP header '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Add HTTP header '%1: %2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 4 — Start to connect to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Start to connect to '%1' with credential of '%2'.

Fields

Name	Description
`str1`	—
`str2`	—

Event ID 5 — Start to connect to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Start to connect to '%1' with default credential.

Fields

Name	Description
`uri`	—

Event ID 6 — Failed to connect to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to connect to '%1' at port %2. The last error is %3: %4

Fields

Name	Description
`uri`	—
`port`	—
`errorCode`	—
`errorMessage`	—

Event ID 7 — Opening request to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Opening request to '%1' to '%2' with flags %3.

Fields

Name	Description
`str1`	—
`str2`	—
`flags`	—

Event ID 8 — Failed to open request to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to open request to '%1'. The last error is %2: %3

Fields

Name	Description
`uri`	—
`port`	—
`errorCode`	—
`errorMessage`	—

Event ID 9 — Request context %1 has request handle %2 to '%3'.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request context %1 has request handle %2 to '%3'.

Fields

Name	Description
`obj1`	—
`obj2`	—
`uri`	—

Event ID 10 — Set HTTP send and receive timeout to %2ms on request handle %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Set HTTP send and receive timeout to %2ms on request handle %1.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 11 — Start to send to request handle %1 with content length %2.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Start to send to request handle %1 with content length %2.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 12 — Request handle %1 completed synchronously.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request handle %1 completed synchronously.

Fields

Name	Description
`obj`	—

Event ID 13 — Request context %1 completed send asynchronously.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request context %1 completed send asynchronously.

Fields

Name	Description
`obj`	—

Event ID 14 — Writing %2 bytes to request handle %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Writing %2 bytes to request handle %1.

Fields

Name	Description
`obj`	—
`length`	—

Event ID 15 — Failed to send entity body to request handle %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to send entity body to request handle %1. The last error is %2: %3

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 16 — Sent HTTP request at request handle %1: %2.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Sent HTTP request at request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 17 — Start to receive response from request handle %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Start to receive response from request handle %1.

Fields

Name	Description
`obj`	—

Event ID 18 — Received HTTP response from request handle %1 with status code %2 and status description '%3'.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Received HTTP response from request handle %1 with status code %2 and status description '%3'.

Fields

Name	Description
`obj`	—
`statusCode`	—
`statusDescription`	—

Event ID 19 — Receive HTTP response from request handle %1: %2.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Receive HTTP response from request handle %1: %2

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 20 — Failed to receive HTTP response from request handle %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Failed to receive HTTP response from request handle %1. The last error is %2: %3

Fields

Name	Description
`obj`	—
`errorCode`	—
`errorMessage`	—

Event ID 21 — Request context %1 received HTTP response of %2 bytes, which is over the %3 limit.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request context %1 received HTTP response of %2 bytes, which is over the %3 limit.

Fields

Name	Description
`obj`	—
`length`	—
`limit`	—

Event ID 22 — Request context %1 resubmitting the request.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request context %1 resubmitting the request.

Fields

Name	Description
`obj`	—

Event ID 23 — Reusing the request handle %1 for server '%2'.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Reusing the request handle %1 for server '%2'.

Fields

Name	Description
`obj`	—
`statusDescription`	—

Event ID 24 — Request context %1 was aborted.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Request context %1 was aborted.

Fields

Name	Description
`obj`	—

Event ID 25 — Progress to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Progress to '%1': %2 stage; %3 retries; %4 bytes sent; %5 total bytes to send; %6 bytes received; %7 total bytes to receive.

Fields

Name	Description
`statusDescription`	—
`stage`	—
`retries`	—
`bytesSent`	—
`totalBytesToSend`	—
`bytesReceived`	—
`totalBytesToReceive`	—

Event ID 26 — HTTP request to '.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

HTTP request to '%1' completed. The error code is %2: %3

Fields

Name	Description
`uri`	—
`hresult`	—
`errorMessage`	—

Event ID 27 — Async operation %1 at %2 failed to process HTTP response '%3'.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 failed to process HTTP response '%3'. The error code is %4: %5

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`response`	—
`hresult`	—
`errorMessage`	—

Event ID 28 — Async operation %1 at %2 started.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 started.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 29 — Async operation %1 at %2 failed to start.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 failed to start. The error code is %3: %4

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`hresult`	—
`errorMessage`	—

Event ID 30 — Async operation %1 at %2 completed successfully.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 completed successfully.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 31 — Async operation %1 at %2 failed with error code %3: %4.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 failed with error code %3: %4

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—
`hresult`	—
`errorMessage`	—

Event ID 32 — Async operation %1 at %2 was canceled.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 was canceled.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 33 — Async operation %1 at %2 was closed.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 was closed.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 34 — Async operation %1 at %2 called progress delegate.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 called progress delegate.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 35 — CompleteDelivery loop with %1 response state; %2 pending receive operations.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

CompleteDelivery loop with %1 response state; %2 pending receive operations.

Fields

Name	Description
`responseState`	—
`pendingReceiveOperations`	—

Event ID 36 — CompleteDelivery enter.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

CompleteDelivery enter.

Event ID 37 — CompleteDelivery exit with %1: %2.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

CompleteDelivery exit with %1: %2

Fields

Name	Description
`hresult`	—
`errorMessage`	—

Event ID 38 — Flush enter.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Flush enter.

Event ID 39 — Flush exit with %1: %2.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Flush exit with %1: %2

Fields

Name	Description
`hresult`	—
`errorMessage`	—

Event ID 40 — Decrement pending receive operations to %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Decrement pending receive operations to %1.

Fields

Name	Description
`pendingOperations`	—

Event ID 41 — Increment pending receive operations to %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Increment pending receive operations to %1.

Fields

Name	Description
`pendingOperations`	—

Event ID 42 — Set response state to %1.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Set response state to %1.

Fields

Name	Description
`responseState`	—

Event ID 43 — Handle %1: HTTP/2 enabled.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Handle %1: HTTP/2 enabled.

Fields

Name	Description
`obj`	—

Event ID 44 — Async operation %1 at %2 started server custom validation.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 started server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 45 — Async operation %1 at %2 waiting for completion of server custom validation.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 waiting for completion of server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 46 — Async operation %1 at %2 failed server custom validation.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 failed server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 47 — Async operation %1 at %2 successfully completed server custom validation.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

Async operation %1 at %2 successfully completed server custom validation.

Fields

Name	Description
`asyncOperation`	—
`asyncObject`	—

Event ID 48 — A dialog cannot be displayed because the parent window handle cannot be determined.

Provider: Microsoft-Windows-Runtime-Web-Http
Channel: Tracing

Message

A dialog cannot be displayed because the parent window handle cannot be determined.