响应
接口在
抓取 API
represents the response to a request.
You can create a new
响应
对象使用
Response.Response()
constructor, but you are more likely to encounter a
响应
object being returned as the result of another API operation—for example, a service worker
Fetchevent.respondWith
, or a simple
WindowOrWorkerGlobalScope.fetch()
.
Response()
响应
对象。
Response.headers
只读
头
object associated with the response.
Response.ok
只读
200
–
299
) or not.
Response.redirected
只读
Indicates whether or not the response is the result of a redirect (that is, its URL list has more than one entry).
Response.status
只读
200
for a success).
Response.statusText
只读
OK
for
200
).
Response.trailers
Promise
resolving to a
头
object, associated with the response with
Response.headers
for values of the HTTP
Trailer
头。
Response.type
只读
basic
,
cors
).
Response.url
只读
The URL of the response.
Response.useFinalURL
A boolean indicating whether this is the final URL of the response.
响应
实现
Body
, so it also has the following properties available to it:
Body.body
只读
ReadableStream
of the body contents.
Body.bodyUsed
只读
布尔
that declares whether the body has been used in a response yet.
Response.clone()
响应
对象。
Response.error()
响应
object associated with a network error.
Response.redirect()
Creates a new response with a different URL.
响应
实现
Body
, so it also has the following methods available to it:
Body.arrayBuffer()
响应
stream and reads it to completion. It returns a promise that resolves with an
ArrayBuffer
.
Body.blob()
响应
stream and reads it to completion. It returns a promise that resolves with a
Blob
.
Body.formData()
响应
stream and reads it to completion. It returns a promise that resolves with a
FormData
对象。
Body.json()
响应
stream and reads it to completion. It returns a promise that resolves with the result of parsing the body text as
JSON
.
Body.text()
响应
stream and reads it to completion. It returns a promise that resolves with a
USVString
(text).
In our
basic fetch example
(
run example live
) we use a simple
fetch()
call to grab an image and display it in an
<img>
element. The
fetch()
call returns a promise, which resolves to the
响应
object associated with the resource fetch operation.
You'll notice that since we are requesting an image, we need to run
Body.blob
(
响应
implements Body) to give the response its correct MIME type.
const image = document.querySelector('.my-image');
fetch('flowers.jpg').then(function(response) {
return response.blob();
}).then(function(blob) {
const objectURL = URL.createObjectURL(blob);
image.src = objectURL;
});
还可以使用
Response.Response()
constructor to create your own custom
响应
对象:
const response = new Response();
| 规范 | 状态 | 注释 |
|---|---|---|
|
Fetch
The definition of 'Response' in that specification. |
实时标准 | 初始定义 |
| 桌面 | 移动 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
响应
|
Chrome
42
|
Edge ≤18 |
Firefox
39
|
IE No |
Opera
29
|
Safari 10.1 | WebView Android 42 |
Chrome Android
42
|
Firefox Android
39
|
Opera Android
29
|
Safari iOS 10.3 | Samsung Internet Android 4.0 |
Response()
构造函数
|
Chrome
42
|
Edge 15 |
Firefox
39
|
IE No |
Opera
29
|
Safari 10.1 | WebView Android 42 |
Chrome Android
42
|
Firefox Android Yes |
Opera Android
29
|
Safari iOS 10.3 | Samsung Internet Android 4.0 |
clone
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
error
|
Chrome Yes | Edge 16 | Firefox Yes | IE No | Opera Yes | Safari Yes | WebView Android No | Chrome Android No | Firefox Android No | Opera Android No | Safari iOS No | Samsung Internet Android No |
headers
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android 42 | Firefox Android No |
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
ok
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari 10.1 | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS 10.3 | Samsung Internet Android No |
redirect
|
Chrome Yes | Edge 16 | Firefox Yes | IE No | Opera Yes | Safari Yes | WebView Android No | Chrome Android No | Firefox Android No | Opera Android No | Safari iOS No | Samsung Internet Android No |
redirected
|
Chrome 60 | Edge 16 | Firefox 49 | IE No | Opera 47 | Safari No | WebView Android 60 | Chrome Android 60 | Firefox Android 49 | Opera Android 44 | Safari iOS No | Samsung Internet Android 8.0 |
status
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari 10.1 | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS 10.3 | Samsung Internet Android No |
statusText
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
trailer
|
Chrome No | Edge No | Firefox ? | IE No | Opera ? | Safari ? | WebView Android No | Chrome Android No | Firefox Android ? | Opera Android ? | Safari iOS ? | Samsung Internet Android No |
type
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
url
|
Chrome
42
|
Edge 14 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android No | Firefox Android No |
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
useFinalURL
弃用
|
Chrome
42
|
Edge ≤18 |
Firefox
39
|
IE No |
Opera
29
|
Safari No | WebView Android No | Chrome Android No |
Firefox Android
39
|
Opera Android
29
|
Safari iOS No | Samsung Internet Android No |
完整支持
不支持
兼容性未知
实验。期望将来行为有所改变。
弃用。不要用于新网站。
用户必须明确启用此特征。