Fetch
suggest changeSyntax
- promise = fetch(url).then(function(response) {})
- promise = fetch(url, options)
- promise = fetch(request)
Parameters
| Options | Details |
|---|---|
| method | The HTTP method to use for the request. ex: GET, POST, PUT, DELETE, HEAD. Defaults to GET. |
| headers | A Headers object containing additional HTTP headers to include in the request. |
| body | The request payload, can be a string or a FormData object. Defaults to undefined |
| cache | The caching mode. default, reload, no-cache |
| referrer | The referrer of the request. |
| mode | cors, no-cors, same-origin. Defaults to no-cors. |
| credentials | omit, same-origin, include. Defaults to omit. |
| redirect | follow, error, manual. Defaults to follow. |
| integrity | Associated integrity metadata. Defaults to empty string. |
Remarks
The Fetch standard defines requests, responses, and the process that binds them: fetching.
Among other interfaces, the standard defines Request and Response Objects, designed to be used for all operations involving network requests.
A useful application of these interfaces is GlobalFetch, which can be used to load remote resources.
For browsers that do not yet support the Fetch standard, GitHub has a polyfill available. In addition, there is also a Node.js implementation that is useful for server/client consistency.
In the absence of cancelable Promises you can’t abort the fetch request (github issue). But there is a proposal by the T39 in stage 1 for cancelable promises.
Found a mistake? Have a question or improvement idea?
Let me know.
Table Of Contents