如何在Chrome扩展Manifest V3中使用modifyHeader规则将tabId添加至请求头

Great question! The shift from webRequest to declarativeNetRequest (DNR) in Manifest V3 does bring limitations when working with dynamic values like tabId—since DNR rules are static by design, you can’t directly reference runtime variables in them. But there are two solid workarounds to achieve your goal, depending on your needs:

Workaround 1: Use webRequest.onBeforeSendHeaders (Recommended, Simpler) #

Even in Manifest V3, the webRequest API still lets you access tabId directly in listener callbacks, making this the easiest way to inject the header. Here’s how to set it up:

1. Update your manifest.json with required permissions:

{
  "manifest_version": 3,
  "name": "Tab ID Header Injector",
  "version": "1.0",
  "permissions": ["webRequest", "webRequestBlocking", "tabs"],
  "host_permissions": ["http://*/*", "https://*/*"],
  "background": {
    "service_worker": "background.js"
  }
}

2. Add the listener in your service worker (background.js):

chrome.webRequest.onBeforeSendHeaders.addListener(
  (details) => {
    // Skip requests that don't come from a tab (e.g., background service worker requests)
    if (details.tabId !== -1) {
      details.requestHeaders.push({
        name: 'X-SomeInfo-TabId',
        value: details.tabId.toString()
      });
    }
    return { requestHeaders: details.requestHeaders };
  },
  { urls: ['http://*/*'], resourceTypes: ['main_frame'] },
  ['blocking', 'requestHeaders', 'extraHeaders']
);

Key Notes: #

• The extraHeaders flag is required in Manifest V3 to modify custom headers like X-SomeInfo-TabId.
• Requests without a linked tab (like those initiated by the extension itself) will have tabId = -1—you can adjust the logic to handle these as needed.

Workaround 2: Dynamic DNR Rules (Advanced, For DNR-Specific Use Cases) #

If you specifically need to use DNR (e.g., for performance optimizations), you can dynamically create and remove rules as tabs are opened and closed. This is more complex but feasible:

1. Update manifest.json for DNR permissions:

{
  "manifest_version": 3,
  "name": "Dynamic Tab ID DNR Injector",
  "version": "1.0",
  "permissions": ["declarativeNetRequest", "tabs"],
  "host_permissions": ["http://*/*"],
  "background": {
    "service_worker": "background.js"
  },
  "declarative_net_request": {
    "rule_resources": [] // We'll only use dynamic rules here
  }
}

2. Manage dynamic rules in background.js:

// Track active tab rules to avoid duplicates
const activeTabRules = new Map();

// Create a DNR rule when a tab is created
chrome.tabs.onCreated.addListener(async (tab) => {
  if (tab.id && tab.url?.startsWith('http')) {
    const ruleId = tab.id; // Use tabId as rule ID for easy tracking
    const newRule = {
      id: ruleId,
      priority: 1,
      action: {
        type: 'modifyHeaders',
        requestHeaders: [{
          header: 'X-SomeInfo-TabId',
          operation: 'set',
          value: tab.id.toString()
        }]
      },
      condition: {
        tabIds: [tab.id],
        regexFilter: `http://${url}/.*`, // Match your target URL pattern
        resourceTypes: ['main_frame']
      }
    };

    await chrome.declarativeNetRequest.updateDynamicRules({
      addRules: [newRule]
    });
    activeTabRules.set(tab.id, ruleId);
  }
});

// Remove the rule when a tab is closed
chrome.tabs.onRemoved.addListener(async (tabId) => {
  const ruleId = activeTabRules.get(tabId);
  if (ruleId) {
    await chrome.declarativeNetRequest.updateDynamicRules({
      removeRuleIds: [ruleId]
    });
    activeTabRules.delete(tabId);
  }
});

Caveats: #

• Manifest V3 limits dynamic DNR rules to 500, so this isn’t ideal for users who keep many tabs open.
• You’ll need to handle edge cases like tabs navigating to non-target URLs or reloading to ensure rules stay accurate.

Why DNR Can’t Do This Natively #

DNR rules are static by design—they’re parsed at extension load time (or when dynamic rules are updated) and can’t reference runtime values like tabId directly. This is part of the performance improvements in Manifest V3, but it means dynamic values require extra workarounds.

内容的提问来源于stack exchange，提问作者Paul Kamp