Allows ASP. NET MVC to be accessed across domains without using JSONP

A cross-domain problem occurs only when JavaScript initiates an Ajax call, or when Silverlight initiates a service invocation, because the browser is given a lower permission for both requests, usually allowing only the resources in the domain to be called. Unless the target server explicitly tells it to allow cross-domain calls.

Therefore, the cross-domain problem is caused by the behavior of the browser, but the solution is on the server side. Because it is not possible to require all clients to reduce security.

Solution Solutions

For the ASP. NET MVC project type, I did some research to make sure that the following scenario is feasible.

For ASP. NET MVC, just add the following in Web. config

<system.webServer>

<customHeaders>

<add name= "Access-control-allow-origin" value= "*"/> <!--<add name= "Access-control-allow-origin" value= " http://localhost:24066 "/>value can set access only to a domain name, only one value--

<add name= "Access-control-allow-headers" value= "Content-type"/>

<add name= "Access-control-allow-methods" value= "GET, POST, PUT, DELETE, OPTIONS"/>

</customHeaders>

</system.webServer>

Allows ASP. NET MVC to be accessed across domains without using JSONP