webRequest.BlockingResponse 编辑
An object of this type is returned by event listeners that have set "blocking"
in their extraInfoSpec
argument.
By setting particular properties in BlockingResponse
, the listener can modify network requests.
Note that you can't set all this object's properties in every listener: the properties you can set are dependent on the event that triggered this listener, as detailed below.
Type
Values of this type are objects. They contain the following properties:
authCredentials
Optionalobject
. If set, the request is made using the given credentials. You can only set this property inonAuthRequired
. TheauthCredentials
property is an object with the following properties:username
string
. Username to supply.password
string
. Password to supply.
cancel
Optionalboolean
. Iftrue
, the request is cancelled. You can only set this property inonBeforeRequest
,onBeforeSendHeaders
,onHeadersReceived
, andonAuthRequired
.redirectUrl
Optionalstring
. This is a URL, and if set, the original request is redirected to that URL. You can only set this property inonBeforeRequest
oronHeadersReceived
.- Redirections to non-HTTP schemes such as data: are allowed, but they are not currently supported (bug 707624). Redirects use the same request method as the original request unless initiated from
onHeadersReceived
stage, in which case the redirect uses the GET method. - If an extension wants to redirect a public (e.g. HTTPS) URL to an extension page, the extension's manifest.json file must contain a web_accessible_resources key that lists the URL for the extension page..
requestHeaders
OptionalwebRequest.HttpHeaders
. This is anHttpHeaders
object, an array in which each object represents a header. If set, the request is made with these headers rather than the original headers. You can only set this property inonBeforeSendHeaders
.responseHeaders
OptionalwebRequest.HttpHeaders
. This is anHttpHeaders
object, an array in which each object represents a header. If set, the server is assumed to have responded with these response headers instead of the originals. You can only set this property inonHeadersReceived
. If multiple extensions attempt to set the same header (for example,Content-Security-Policy
), only one of the changes will be successful.upgradeToSecure
Optionalboolean
. If set totrue
and the original request is an HTTP request, this will prevent the original request from being sent and instead make a secure (HTTPS) request. If any extension returnsredirectUrl
inonBeforeRequest
, thenupgradeToSecure
will be ignored for that request. You can only set this property inonBeforeRequest
.
Browser compatibility
BCD tables only load in the browser
AcknowledgementsThis API is based on Chromium's chrome.webRequest
API. This documentation is derived from web_request.json
in the Chromium code.
// Copyright 2015 The Chromium Authors. All rights reserved. // // Redistribution and use in source and binary forms, with or without // modification, are permitted provided that the following conditions are // met: // // * Redistributions of source code must retain the above copyright // notice, this list of conditions and the following disclaimer. // * Redistributions in binary form must reproduce the above // copyright notice, this list of conditions and the following disclaimer // in the documentation and/or other materials provided with the // distribution. // * Neither the name of Google Inc. nor the names of its // contributors may be used to endorse or promote products derived from // this software without specific prior written permission. // // THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS // "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT // LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR // A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT // OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, // SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT // LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, // DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY // THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论