如何在Chrome扩展中调用chrome.cookies.set()设置已保存的批量Cookie

1. 核心错误：Cookie URL 构造不符合规则 #

你当前强制写死https:// + domain的方式有两个问题：

• 如果原Cookie的secure属性为false（对应HTTP站点的Cookie），用HTTPS开头的URL完全无法写入对应Cookie
• 如果原Cookie的domain带前导点（比如.example.com），拼接出的https://.example.com是非法URL，直接导致set操作失败
  正确构造URL的逻辑：
• 优先根据secure属性选择http://或https://前缀
• 去除domain开头的前导点再拼接

2. HostOnly 类型Cookie处理错误 #

HostOnly类型的Cookie不允许手动指定domain参数，如果你要写入的原Cookie是hostOnly: true的类型，构造set参数时必须去掉domain字段，Chrome会自动根据你传入的url生成对应hostOnly的Cookie。

3. 异步操作顺序混乱 #

chrome.cookies.remove和chrome.cookies.set都是异步API，你当前的写法没有等待删除操作完成就执行写入，很容易出现Cookie冲突、写入被覆盖的问题。建议将Chrome回调式API转为Promise，用async/await控制执行顺序。

4. 排查错误的必要手段 #

给chrome.cookies.set加上回调打印错误信息，可以直接定位具体失败原因：

chrome.cookies.set(c, (result) => {
  if (chrome.runtime.lastError) {
    console.error("Cookie设置失败:", chrome.runtime.lastError, c);
  }
});

修复后的代码示例 #

// 先封装Chrome Cookie API为Promise，方便控制异步顺序
const cookiesGetAll = (details) => new Promise(resolve => chrome.cookies.getAll(details, resolve));
const cookiesRemove = (details) => new Promise(resolve => chrome.cookies.remove(details, resolve));
const cookiesSet = (details) => new Promise(resolve => chrome.cookies.set(details, resolve));

async function handleActivated(activeInfo) {
    console.log("Tab " + activeInfo.tabId + " was activated. From: " + getSession(activeInfo.tabId));
    const targetSession = getSession(activeInfo.tabId);
    if (targetSession === currentActiveSession) return;

    const lastActiveSession = currentActiveSession;
    currentActiveSession = targetSession;
    console.log("last session: " + lastActiveSession + " | current session: " + currentActiveSession);

    // 保存上一个会话的Cookie
    const currentCookies = await cookiesGetAll({});
    sessionDictionary[lastActiveSession]["cookieStore"] = currentCookies;

    // 清空当前所有Cookie
    for (const removedCookie of currentCookies) {
        const protocol = removedCookie.secure ? "https://" : "http://";
        const cleanDomain = removedCookie.domain.replace(/^\./, '');
        const urlString = protocol + cleanDomain;
        await cookiesRemove({ url: urlString, name: removedCookie.name });
    }

    // 写入当前会话的Cookie
    const cookiesToSet = sessionDictionary[currentActiveSession]["cookieStore"];
    for (const cookie of cookiesToSet) {
        const protocol = cookie.secure ? "https://" : "http://";
        const cleanDomain = cookie.domain.replace(/^\./, '');
        const urlString = protocol + cleanDomain;
        
        const c = {
            expirationDate: cookie.expirationDate,
            httpOnly: cookie.httpOnly,
            name: cookie.name,
            path: cookie.path,
            sameSite: cookie.sameSite,
            secure: cookie.secure,
            storeId: cookie.storeId,
            url: urlString,
            value: cookie.value
        };
        // 非hostOnly的Cookie才加domain参数
        if (!cookie.hostOnly) {
            c.domain = cookie.domain;
        }
        await cookiesSet(c);
    }
}

额外注意事项 #

如果你的扩展是Manifest V3版本，注意<all_urls>权限不能放在permissions数组中，必须放到host_permissions字段下才会生效。

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