Ajax cross-Domain Problem Resolution (1)-prohibit browser from cross-domain restrictions

Idea: Modify the browser startup parameters from the command line so that the browser does not cross-domain checks, allowing cross-domain

Method: Command line arguments to start the browser after adding parameters--disable-web-security

Cases:
Chrome--disable-web-security

The role of the--disabl-web-security parameter is to disallow cross-domain checking by the browser

However, there are three drawbacks to this approach:

1. Every time you start a browser, you need to start it from the command line, too cumbersome

2. This approach can lead to security issues

3. This method is a client-side change, in the actual use, on each client to prohibit the browser cross-domain inspection is not very realistic, so less practical.

In general, although the method can solve the cross-domain problem, but the value is not very large. In the actual project, the main server-side changes make it possible to support cross-domain.

Ajax cross-Domain Problem Resolution (1)-prohibit browser from cross-domain restrictions