Authorization challenge for HTTP status code 401 or 407.

Response to an AuthChallenge.

A cookie with was not sent with a request with the corresponding reason.

A cookie which was not stored from a response with the corresponding reason.

Information about the cached resource.

Cookie object

Cookie parameter object

Fired when data chunk was received over the network.

Fired when EventSource message is received.

Request / response headers as keys / values of JSON object.

Information about the request initiator.

Fired when HTTP request has failed to load.

Fired when HTTP request has finished loading.

An options object that may be extended later to better support CORS, CORB and streaming.

An object providing the result of a network resource load.

Post data entry for HTTP request

An object representing a report generated by the Reporting API.

Is sent whenever a new report is added. And after 'enableReportingApi' for all existing reports.

HTTP request data.

Details of an intercepted HTTP request, which must be either allowed, blocked, modified or mocked. Deprecated, use Fetch.requestPaused instead.

Request pattern for interception.

Fired if request ended up loading from cache.

Fired when page is about to send HTTP request.

Fired when additional information about a requestWillBeSent event is available from the network stack. Not every requestWillBeSent event will have an additional requestWillBeSentExtraInfo fired for it, and there is no guarantee whether requestWillBeSent or requestWillBeSentExtraInfo will be fired first for the same request.

Fired when resource loading priority is changed

Timing information for the request.

HTTP response data.

Fired when HTTP response is available.

Fired when additional information about a responseReceived event is available from the network stack. Not every responseReceived event will have an additional responseReceivedExtraInfo for it, and responseReceivedExtraInfo may be fired before or after responseReceived.

Security details about a request.

Details of a signed certificate timestamp (SCT).

Information about a signed exchange response.

Information about a signed exchange header. https://wicg.github.io/webpackage/draft-yasskin-httpbis-origin-signed-exchanges-impl.html#cbor-representation

Information about a signed exchange response.

Fired when a signed exchange was received over the network

Information about a signed exchange signature. https://wicg.github.io/webpackage/draft-yasskin-httpbis-origin-signed-exchanges-impl.html#rfc.section.3.1

Fired when request for resources within a .wbn file failed.

Fired when handling requests for resources within a .wbn file. Note: this will only be fired for resources that are requested by the webpage.

Fired once when parsing the .wbn file has failed.

Fired once when parsing the .wbn file has succeeded. The event contains the information about the web bundle contents.

Fired exactly once for each Trust Token operation. Depending on the type of the operation and whether the operation succeeded or failed, the event is fired before the corresponding request was sent or after the response was received.

Determines what type of Trust Token operation is executed and depending on the type, some additional parameters. The values are specified in third_party/blink/renderer/core/fetch/trust_token.idl.

Fired when WebSocket is closed.

Fired upon WebSocket creation.

WebSocket message data. This represents an entire WebSocket message, not just a fragmented frame as the name suggests.

Fired when WebSocket message error occurs.

Fired when WebSocket message is received.

Fired when WebSocket message is sent.

Fired when WebSocket handshake response becomes available.

WebSocket request data.

WebSocket response data.

Fired when WebSocket is about to initiate handshake.

Fired when WebTransport is disposed.

Fired when WebTransport handshake is finished.

Fired upon WebTransport creation.

The reason why request was blocked.

Whether the request complied with Certificate Transparency policy.

The underlying connection technology that the browser is supposedly using.

List of content encodings supported by the backend.

Types of reasons why a cookie may not be sent with a request.

Represents the cookie's 'Priority' status: https://tools.ietf.org/html/draft-west-cookie-priority-00

Represents the cookie's 'SameSite' status: https://tools.ietf.org/html/draft-west-first-party-cookies

Represents the source scheme of the origin that originally set the cookie. A value of "Unset" allows protocol clients to emulate legacy cookie scope for the scheme. This is a temporary ability and it will be removed in the future.

The reason why request was blocked.

Network level fetch failure reason.

Unique intercepted request identifier.

Stages of the interception to begin intercepting. Request will intercept before the request is sent. Response will intercept after the response is received.

Unique loader identifier.

Monotonically increasing time in seconds since an arbitrary point in the past.

The status of a Reporting API report.

Unique request identifier.

Loading priority of a resource request.

Resource type as it was perceived by the rendering engine.

Source of serviceworker response.

Types of reasons why a cookie may not be stored from a response.

Field type for a signed exchange related error.

UTC time in seconds, counted from January 1, 1970.