Api and WebService cross-Origin
In many cases, cross-origin problems occur when you call a webapi through ajax. If you want to use ajax to call the same WebService, you also need an Interface Cross-origin problem. The solution is as follows:
1. IIS configuration
Open IIS and select the published webapi or WebService. Select website> HTTP Response Header> Add .. The procedure is as follows:
The name and value to be added are
<Add name = "Access-Control-Allow-Methods" value = "OPTIONS, POST, GET"/>
<Add name = "Access-Control-Allow-Headers" value = "x-requested-with, Content-Type"/>
<Add name = "Access-Control-Allow-Origin" value = "*"/>
2. Add tags directly in web. config.
<System. webServer>
<HttpProtocol>
<CustomHeaders>
<Add name = "Access-Control-Allow-Methods" value = "OPTIONS, POST, GET"/>
<Add name = "Access-Control-Allow-Headers" value = "x-requested-with, Content-Type"/>
<Add name = "Access-Control-Allow-Origin" value = "*"/>
</CustomHeaders>
</HttpProtocol>
</System. webServer>
Remember .. Only one method can be used. Otherwise, an error is reported.