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
Table of contents 1. Install Docker 2. Install Gi...
We usually have a scanning box when we open the c...
Environment: VMware VCSA 6.7 (VMware-VCSA-all-6.7...
First of all, you need to know some characteristi...
When we make a gradient background color, we will...
Table of contents Design scenario Technical Point...
IIS7 needs to confirm whether the "URL REWRI...
Table of contents 1. What are microtasks? 2. What...
Let's take a look at zabbix monitoring sqlser...
In many cases, in order to beautify the form, the ...
Introduction Incremental backup means that after ...
This article uses examples to describe the basic ...
When setting the text in the search text box, the...
Table of contents Problem Description Principle A...
Table of contents 1. Get request: 2. Post request...