mode read-only property of the
interface contains the mode of the request (e.g.,
websocket.) This is used
to determine if cross-origin requests lead to valid responses, and which properties of the response are readable.
The associated mode, available values of which are:
If a request is made to another origin with this mode set, the result is an error. You could use this to ensure that a request is always being made to your origin.
Prevents the method from being anything other than
Response. This ensures that ServiceWorkers do not affect the semantics of the Web and prevents security and privacy issues arising from leaking data across domains.
Allows cross-origin requests, for example to access various APIs offered by 3rd party vendors. These are expected to adhere to the CORS protocol. Only a limited set of headers are exposed in the
Response, but the body is readable.
A mode for supporting navigation. The
navigatevalue is intended to be used only by HTML navigation. A navigate request is created only while navigating between documents.
A special mode used only when establishing a WebSocket connection.
Requests can be initiated in a variety of ways, and the mode for a request depends on the particular means by which it was initiated.
For example, when a
Request object is created using the
Request() constructor, the value of the
Request is set to
However, for requests created other than by the
no-cors is typically used as the mode; for example, for
embedded resources where the request is initiated from markup, unless the
attribute is present, the request is in most cases made using the
mode — that is, for the
(except when used with modules), or
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 save the request mode in a variable:
const myRequest = new Request("flowers.jpg"); const myMode = myRequest.mode; // returns "cors" by default
|Fetch Standard |
BCD tables only load in the browser