Chrome disables browser cross-domain interception

Chrome cross-domain settings after version number 49

After the version of Chrome has risen to 49, the cross-domain setting is stricter than before, and a directory of new user personal information needs to be given after the--disable-web-security is added to the command. It is well known that Chrome is a browser that needs to be signed in with a Gmail address, which will generate a directory where personal information is stored and personal information such as a user's collection, history, and so on. After version 49, if you set up a Chrome browser to support cross-domain mode, you need to specify a personal information directory, not the default directory, it is estimated that Chrome browser is afraid that users do not use cross-domain mode to disclose their personal information (mainly cookies, Many websites ' login token information is stored in a cookie.

Specific practices are:

1. Create a new directory on your computer, for example: C:\MyChromeDevUserData

2. Add the--disable-web-security--user-data-dir=c:\mychromedevuserdata,--user-data-dir value in the target input box in the Properties page to the new directory you just created.

3. Click Apply and OK to close the Properties page and open the Chrome browser.

Open Chrome again and find "--disable-web-security" related hints that chrome can work across domains again.

Reference: http://www.cnblogs.com/laden666666/p/5544572.html

This article is from the "Jodyrex" blog, make sure to keep this source http://503431920.blog.51cto.com/6681280/1890414

Chrome disables browser cross-domain interception