The following code introduces Chrome's monitoring of cookie changes. The code is as follows: /** * Monitor cookie changes */ chrome.cookies.onChanged.addListener(function(changeInfo){ // cookies.onChanged listens to all cookies, so we need to filter and process only our website's own cookies if(GhomepageDomain == changeInfo.cookie.domain){ var cookieNameReg = /[AZ]/; var cookieInfo = changeInfo.cookie; if(!cookieNameReg.test(cookieInfo.name)){ //Copy all lowercase cookie names to plugin if(changeInfo.removed){ // Remove cookies chrome.cookies.remove({ url : Gplugin, name : cookieInfo['name'] },function(_cookie){ // console.log('remove, re-acquire cookie',_cookie); // getUserInfo(1); }); }else{ // Set cookies chrome.cookies.set({ url: Gplugin, name: cookieInfo['name'], path: '/', value: cookieInfo['value'], expirationDate: cookieInfo['expirationDate'], secure: true, sameSite: 'no_restriction', // Do not block cross-domain cookies },function(_cookie){ // console.log('Set, re-obtain cookie',_cookie); // getUserInfo(1); }); } } } }); ps: Let's take a look at the cookie monitoring and assignment issues of CHROME extension notes. Cookie monitoring and assignment operations require permissions to be declared in the manifest file. { "permissions": [ "cookies", "*://*.Domain name to operate cookies.com/*" ], } /** * Monitor cookie changes */ chrome.cookies.onChanged.addListener(function(changeInfo){ // cookies.onChanged listens to all cookies, so we need to filter and process only our website's own cookies if(GhomepageDomain == changeInfo.cookie.domain){ var cookieNameReg = /[AZ]/; var cookieInfo = changeInfo.cookie; if(!cookieNameReg.test(cookieInfo.name)){ //Copy all lowercase cookie names to plugin if(changeInfo.removed){ // Remove cookies chrome.cookies.remove({ url : Gplugin, name : cookieInfo['name'] },function(_cookie){ // console.log('remove, re-acquire cookie',_cookie); // getUserInfo(1); }); }else{ // Set cookies chrome.cookies.set({ url: Gplugin, name: cookieInfo['name'], path: '/', value: cookieInfo['value'], expirationDate: cookieInfo['expirationDate'], secure: true, sameSite: 'no_restriction', // Do not block cross-domain cookies. If secure and sameSite are not available, the iframe page will not be able to use cooke in chrome 80 and above. },function(_cookie){ // console.log('Set, re-obtain cookie',_cookie); // getUserInfo(1); }); } } } }); Note: For those who don't understand secure and sameSite, please read Liao Xuefeng's blog on the SameSite attribute of cookies This is the end of this article about Chrome's monitoring of cookie changes and assignment issues. For more relevant content about Chrome's monitoring of cookie changes, please search for previous articles on 123WORDPRESS.COM or continue to browse the following related articles. I hope everyone will support 123WORDPRESS.COM in the future! You may also be interested in:
|
<<: Analysis and solution of the reason why overflow-y: visible; does not work in CSS
>>: Installation process of zabbix-agent on Kylin V10
Preface Recently I encountered a deadlock problem...
As more and more projects are deployed, more and ...
Table of contents 1. Page Rendering 2. Switch tag...
Purpose: Nested use of MySQL aggregate functions ...
Preface In general development, images are upload...
Why do we need to summarize the browser compatibi...
1. Install the cross-system file transfer tool un...
Technology Fan html web page, you must know vue f...
Table of contents Event-driven and publish-subscr...
Environment: (docker, k8s cluster), continue with...
Table of contents Preface Check Constraints Creat...
The syntax for an outer join is as follows: SELEC...
Table of contents 1. Scene introduction 2 Code Op...
Table of contents Preface 1. Life cycle in Vue2 I...
1. Background During the server development proce...