Response

Constructor

Syntax

new Response(body, init)

Parameters

  • body (optional): An object that defines the body text for the response. Can be null or one of these values: _ BufferSource _ FormData _ ReadableStream _ URLSearchParams * USVString
  • init (optional): An options object that contains custom settings to apply to the response. Valid options are: _ status: The status code for the reponse, such as, 200. _ statusText: The status message associated with the status code, like, OK. * headers: Any headers to add to your response that are contained within a Headers object or object literal of ByteString key/value pairs.

Properties

  • body: A simple getter used to expose a ReadableStream of the body contents.
  • bodyUsed: A Boolean value that declares if the body was used in a response.
  • headers: Contains the associated Headers object for the request.
  • ok: Contains a Boolean value to indicate if the response was successful (status in the range 200-299).
  • redirected: Indicates if the response is the result of a redirect, that is, its URL list has more than one entry.
  • status: Contains the status code of the response (for example, 200 to indicate success).
  • statusText: Contains the status message that corresponds to the status code (for example, OK for 200).
  • url: Contains the URL of the response. The value of the url property is the final URL obtained after any redirects.
  • webSocket: This is present in successful WebSocket handshake responses. For example, if a client sends a WebSocket upgrade request to an origin and a worker intercepts the request and then forwards it to the origin and the origin replies with a successful WebSocket upgrade response, the worker sees response.webSocket. This establishes a WebSocket connection proxied through a worker. Note that you cannot intercept data flowing over a WebSocket connection.

Methods