Package org.openqa.selenium.devtools.v128.network.model
package org.openqa.selenium.devtools.v128.network.model
-
ClassDescriptionThe reason why Chrome uses a specific transport protocol for HTTP semantics.A cookie associated with the request which may or may not be sent with it.Authorization challenge for HTTP status code 401 or 407.Response to an AuthChallenge.The reason why request was blocked.A cookie which was not stored from a response with the corresponding reason.Information about the cached resource.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.Cookie objectTypes of reasons why a cookie may not be sent with a request.Types of reasons why a cookie should have been blocked by 3PCD but is exempted for the request.Cookie parameter objectcookiePartitionKey object The representation of the components of the key that are created by the cookiePartitionKey class contained in net/cookies/cookie_partition_key.h.Represents the cookie's 'Priority' status: https://tools.ietf.org/html/draft-west-cookie-priority-00Represents the cookie's 'SameSite' status: https://tools.ietf.org/html/draft-west-first-party-cookiesRepresents the source scheme of the origin that originally set the cookie.The reason why request was blocked.Fired when data chunk was received over the network.Network level fetch failure reason.Fired when EventSource message is received.A cookie should have been blocked by 3PCD but is exempted and stored from a response with the corresponding reason.Request / response headers as keys / values of JSON object.Information about the request initiator.Unique intercepted request identifier.Stages of the interception to begin intercepting.Unique loader identifier.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.Monotonically increasing time in seconds since an arbitrary point in the past.Post data entry for HTTP requestAn object representing a report generated by the Reporting API.The status of a Reporting API report.HTTP request data.Unique request identifier.Deprecated.Request pattern for interception.Fired when page is about to send HTTP request.Fired when additional information about a requestWillBeSent event is available from the network stack.Fired when resource loading priority is changedLoading priority of a resource request.Timing information for the request.Resource type as it was perceived by the rendering engine.HTTP response data.Fired when HTTP response is available.Fired when 103 Early Hints headers is received in addition to the common response.Fired when additional information about a responseReceived event is available from the network stack.Security details about a request.Source of serviceworker response.Source of service worker router.Types of reasons why a cookie may not be stored from a response.Details of a signed certificate timestamp (SCT).Information about a signed exchange response.Field type for a signed exchange related error.Information about a signed exchange header.Information about a signed exchange response.Fired when a signed exchange was received over the networkInformation about a signed exchange signature.Fired when request for resources within a .wbn file failed.Fired when handling requests for resources within a .wbn file.Fired once when parsing the .wbn file has failed.Fired once when parsing the .wbn file has succeeded.UTC time in seconds, counted from January 1, 1970.Fired exactly once for each Trust Token operation.Determines what type of Trust Token operation is executed and depending on the type, some additional parameters.Fired when WebSocket is closed.Fired upon WebSocket creation.WebSocket message data.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.