The method returns null
unless this request has failed, as reported by requestfailed
event.
Usage
Example of logging of all the failed requests:
page.on('requestfailed', request => {
console.log(request.url() + ' ' + request.failure().errorText);
});
An object with the request HTTP headers. The header names are lower-cased. Note that this method does not return
security-related headers, including cookie-related ones. You can use
request.allHeaders() for complete list of
headers that include cookie
information.
An array with all the request HTTP headers associated with this request. Unlike
request.allHeaders(), header names are NOT
lower-cased. Headers with multiple entries, such as Set-Cookie
, appear in the array multiple times.
Whether this request is driving frame's navigation.
Request that was redirected by the server to this one, if any.
When the server responds with a redirect, Playwright creates a new [Request] object. The two requests are connected
by redirectedFrom()
and redirectedTo()
methods. When multiple server redirects has happened, it is possible to
construct the whole redirect chain by repeatedly calling redirectedFrom()
.
Usage
For example, if the website http://example.com
redirects to https://example.com
:
const response = await page.goto('http://example.com');
console.log(response.request().redirectedFrom().url()); // 'http://example.com'
If the website https://google.com
has no redirects:
const response = await page.goto('https://google.com');
console.log(response.request().redirectedFrom()); // null
New request issued by the browser if the server responded with redirect.
Usage
This method is the opposite of request.redirectedFrom():
console.log(request.redirectedFrom().redirectedTo() === request); // true
Returns resource size information for given request.
Returns resource timing information for given request. Most of the timing values become available upon the
response, responseEnd
becomes available when request finishes. Find more information at
Resource Timing API.
Usage
const requestFinishedPromise = page.waitForEvent('requestfinished');
await page.goto('http://example.com');
const request = await requestFinishedPromise;
console.log(request.timing());
Time immediately before the user agent starts establishing the connection to the server to retrieve the resource.
The value is given in milliseconds relative to startTime
, -1 if not available.
Time immediately before the user agent starts establishing the connection to the server to retrieve the resource.
The value is given in milliseconds relative to startTime
, -1 if not available.
Time immediately after the browser starts the domain name lookup for the resource. The value is given in
milliseconds relative to startTime
, -1 if not available.
Time immediately before the browser starts the domain name lookup for the resource. The value is given in
milliseconds relative to startTime
, -1 if not available.
Time immediately before the browser starts requesting the resource from the server, cache, or local resource. The
value is given in milliseconds relative to startTime
, -1 if not available.
Time immediately after the browser receives the last byte of the resource or immediately before the transport
connection is closed, whichever comes first. The value is given in milliseconds relative to startTime
, -1 if not
available.
Time immediately after the browser starts requesting the resource from the server, cache, or local resource. The
value is given in milliseconds relative to startTime
, -1 if not available.
Time immediately before the browser starts the handshake process to secure the current connection. The value is
given in milliseconds relative to startTime
, -1 if not available.
Request start time in milliseconds elapsed since January 1, 1970 00:00:00 UTC
Generated using TypeDoc
Whenever the page sends a request for a network resource the following sequence of events are emitted by [Page]:
If request fails at some point, then instead of
'requestfinished'
event (and possibly instead of 'response' event), the page.on('requestfailed') event is emitted.NOTE HTTP Error responses, such as 404 or 503, are still successful responses from HTTP standpoint, so request will complete with
'requestfinished'
event.If request gets a 'redirect' response, the request is successfully finished with the
requestfinished
event, and a new request is issued to a redirected url.