Movatterモバイル変換


[0]ホーム

URL:


MDN Web Docs

Intercept HTTP requests

To intercept HTTP requests, use thewebRequest API.This API enables you to add listeners for various stages of making an HTTP request.In the listeners, you can:

  • Get access to request headers and bodies and response headers.
  • Cancel and redirect requests.
  • Modify request and response headers.

This article looks at three different uses for thewebRequest module:

  • Logging request URLs as they are made.
  • Redirecting requests.
  • Modifying request headers.

Logging request URLs

To see how you can usewebRequest to log requests, create a new directory called "requests".In that directory, create a file called "manifest.json" and add:

json
{  "description": "Demonstrating webRequests",  "manifest_version": 2,  "name": "webRequest-demo",  "version": "1.0",  "permissions": ["webRequest", "<all_urls>"],  "background": {    "scripts": ["background.js"]  }}

Next, create a file called "background.js" and add:

js
function logURL(requestDetails) {  console.log(`Loading: ${requestDetails.url}`);}browser.webRequest.onBeforeRequest.addListener(logURL, {  urls: ["<all_urls>"],});

You useonBeforeRequest to call thelogURL() function just before starting the request. ThelogURL() function grabs the URL of the request from the event object and logs it to the browser console.The{urls: ["<all_urls>"]}pattern means you intercept HTTP requests to all URLs.

To test it:

In the Browser Console, you should see the URLs for any resources the browser requests.For example, this screenshot shows the URLs from loading a Wikipedia page:

Browser console menu: URLs from extension

Redirecting requests

Now usewebRequest to redirect HTTP requests. First, replace "manifest.json" with this:

json
{  "description": "Demonstrating webRequests",  "manifest_version": 2,  "name": "webRequest-demo",  "version": "1.0",  "permissions": [    "webRequest",    "webRequestBlocking",    "https://developer.mozilla.org/"  ],  "background": {    "scripts": ["background.js"]  }}

The changes here:

  • Add thewebRequestBlockingpermission.This extra permission is needed when an extension wants to modify a request.
  • Replace the<all_urls> permission with individualhost permissions, as this is good practice to minimize the number of requested permissions.

Next, replace "background.js" with this:

js
let pattern = "https://developer.mozilla.org/*";const targetUrl =  "https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Your_second_WebExtension/frog.jpg";function redirect(requestDetails) {  console.log(`Redirecting: ${requestDetails.url}`);  if (requestDetails.url === targetUrl) {    return;  }  return {    redirectUrl: targetUrl,  };}browser.webRequest.onBeforeRequest.addListener(  redirect,  { urls: [pattern], types: ["image"] },  ["blocking"],);

Again, you use theonBeforeRequest event listener to run a function just before each request is made.This function replaces theredirectUrl with the target URL specified in the function. In this case, the frog image from theyour second extension tutorial.

This time you are not intercepting every request: the{urls:[pattern], types:["image"]} option specifies that you only intercept requests (1) to URLs residing under "https://developer.mozilla.org/" and (2) for image resources.SeewebRequest.RequestFilter for more on this.

Also, note that you're passing an option called"blocking": you must pass this whenever you want to modify the request.It makes the listener function block the network request, so the browser waits for the listener to return before continuing.See thewebRequest.onBeforeRequest documentation for more on"blocking".

To test it out, open a page on MDN that contains images (for example,the page listing extension user interface components),reload the extension, and then reload the MDN page. You see something like this:

Images on a page replaced with a frog image

Modifying request headers

Finally, usewebRequest to modify request headers.In this example, you change the "User-Agent" header so the browser identifies itself as Opera 12.16, but only when visiting pages under "https://useragentstring.com/".

Update the "manifest.json" to includehttps://useragentstring.com/ like this:

json
{  "description": "Demonstrating webRequests",  "manifest_version": 2,  "name": "webRequest-demo",  "version": "1.0",  "permissions": [    "webRequest",    "webRequestBlocking",    "https://useragentstring.com/"  ],  "background": {    "scripts": ["background.js"]  }}

Replace "background.js" with code like this:

js
let targetPage = "https://useragentstring.com/*";let ua =  "Opera/9.80 (X11; Linux i686; Ubuntu/14.10) Presto/2.12.388 Version/12.16";function rewriteUserAgentHeader(e) {  e.requestHeaders.forEach((header) => {    if (header.name.toLowerCase() === "user-agent") {      header.value = ua;    }  });  return { requestHeaders: e.requestHeaders };}browser.webRequest.onBeforeSendHeaders.addListener(  rewriteUserAgentHeader,  { urls: [targetPage] },  ["blocking", "requestHeaders"],);

You use theonBeforeSendHeaders event listener to run a function just before the request headers are sent.

The listener function is called only for requests to URLs matching thetargetPagepattern.Also, note that you again pass"blocking" as an option. You also pass"requestHeaders", meaning the listener is passed an array containing the request headers you expect to send.SeewebRequest.onBeforeSendHeaders for more information on these options.

The listener function looks for the "User-Agent" header in the array of request headers, replaces its value with the value of theua variable, and returns the modified array.This modified array is sent to the server.

To test it out, openuseragentstring.com and check that it identifies the browser as Firefox.Then reload the extension, reloaduseragentstring.com, and see that Firefox is now identified as Opera.

useragentstring.com showing details of the modified user agent string

Learn more

To learn about all the things you can do with thewebRequest API, see itsreference documentation.

Help improve MDN

Learn how to contribute.

This page was last modified on byMDN contributors.


[8]ページ先頭

©2009-2025 Movatter.jp