One 、 causes

         as everyone knows ,Chrome Browsers have a kind of cross domain restriction Deep obsession , In the use of XMLHttpRequest or fetch When accessing an external website, you must cooperate with the target server . What surprises me is , There is a special article in Google's official documents about how to remove the cross domain restrictions of the extension program .

Two 、 A functional test

         According to the document , As long as manifest.json Fill in  host_permissions The cross domain restriction can be lifted , It even supports the use of wildcards to lift the cross domain restrictions of all websites .

        However , Unfortunately , When I write it in full accordance with the sample code provided by Google , But prompted to be intercepted .

3、 ... and 、 Hope is dashed

        after 5 Hours of searching , I am here Chrome I found an article in my official blog , Completely shattered my fantasy .Changes to Cross-Origin Requests in Chrome Extension Content Scriptshttps://www.chromium.org/Home/chromium-security/extension-content-script-fetches/

        As part of a broader Extension Manifest V3 effort to improve extension security, privacy, and performance, these cross-origin requests in content scripts will soon be disallowed.

          Which translates as ：

         As a broader Extension list V3 Part of , In order to improve the security of the extension program 、 Privacy and performance , These content scripts （content_script） Cross domain requests in will soon be banned .

          Damn security again .