clone() method of the
Request interface creates a copy of the current
Like the underlying
body of a cloned
will signal backpressure at the rate of the faster consumer of the two bodies,
and unread data is enqueued internally on the slower consumed
without any limit or backpressure.
Beware when you construct a
Request from a stream and then
clone() throws a
TypeError if the request body has already been used. In fact, the main reason
clone() exists is to allow multiple uses of body objects (when they are one-use only.)
If you intend to modify the request, you may prefer the
Request object, which is an exact copy of the
clone() was called on.
In the following snippet, we create a new request using the
Request() constructor (for an image file in the same directory as the script), then clone the request.
const myRequest = new Request('flowers.jpg'); const newRequest = myRequest.clone(); // a copy of the request is now stored in newRequest
|Fetch Standard |
BCD tables only load in the browser