There is always a cross-domain problem, and then there is a JSONP solution, and the code in MVC is as follows:
Public classJsonpResult:System.Web.Mvc.JsonResult {Objectdata =NULL; PublicJsonpresult () {} PublicJsonpresult (Objectdata) { This. data =data; } Public Override voidExecuteresult (ControllerContext controllercontext) {if(ControllerContext! =NULL) {httpresponsebase Response=ControllerContext.HttpContext.Response; Httprequestbase Request=controllerContext.HttpContext.Request; stringCallbackfunction = request["Callback"]; if(string. IsNullOrEmpty (callbackfunction)) {Throw NewException ("Callback function Name must is provided in the request!"); } Response.ContentType="Application/x-javascript"; if(Data! =NULL) {JavaScriptSerializer Serializer=NewJavaScriptSerializer (); Response.Write (string. Format ("{0} ({1});", Callbackfunction, serializer. Serialize (data))); } } } }
In theory, you can also extend the parsing of the JSON itself, for example, you think the default JSON parser is too slow or something.
JSONP extension on MVC to solve cross-domain access issues