This is a known bug with jQuery. The jQuery team has “no plans to support this in core and is better suited as a plugin.” (See this comment). IE does not use the XMLHttpRequest, but an alternative object named XDomainRequest. There is a plugin available to support this in jQuery, which can be found here: … Read more
function foo(data) { // do stuff with JSON } var script = document.createElement(‘script’); script.src=”https://example.com/path/to/jsonp?callback=foo” document.getElementsByTagName(‘head’)[0].appendChild(script); // or document.head.appendChild(script) in modern browsers
After asking this question, I finally found what I needed, so I am answering it. I ran across this JsonpMediaTypeFormatter. Add it into the Application_Start of your global.asax by doing this: var config = GlobalConfiguration.Configuration; config.Formatters.Insert(0, new JsonpMediaTypeFormatter()); and you are good to go with an JQuery AJAX call that looks like this: $.ajax({ url: … Read more
I solved the Access-Control-Allow-Origin error modifying the dataType parameter to dataType:’jsonp’ and adding a crossDomain:true $.ajax({ url: ‘https://www.googleapis.com/moderator/v1/series?key=’+key, data: myData, type: ‘GET’, crossDomain: true, dataType: ‘jsonp’, success: function() { alert(“Success”); }, error: function() { alert(‘Failed!’); }, beforeSend: setHeader });
JSONP is really a simply trick to overcome XMLHttpRequest same domain policy. (As you know one cannot send AJAX (XMLHttpRequest) request to a different domain.) So – instead of using XMLHttpRequest we have to use script HTMLl tags, the ones you usually use to load JS files, in order for JS to get data from … Read more
$.getJSON() is a kind of abstraction of a regular AJAX call where you would have to tell that you want a JSON encoded response. $.ajax({ url: url, dataType: ‘json’, data: data, success: callback }); You can handle errors in two ways: generically (by configuring your AJAX calls before actually calling them) or specifically (with method … Read more
JSONP is JSON with padding. That is, you put a string at the beginning and a pair of parentheses around it. For example: //JSON {“name”:”stackoverflow”,”id”:5} //JSONP func({“name”:”stackoverflow”,”id”:5}); The result is that you can load the JSON as a script file. If you previously set up a function called func, then that function will be called … Read more
Preface: This answer is over six years old. While the concepts and application of JSONP haven’t changed (i.e. the details of the answer are still valid), you should look to use CORS where possible (i.e. your server or API supports it, and the browser support is adequate), as JSONP has inherent security risks. JSONP (JSON … Read more
For the record, as far as I can tell, you had two problems: You weren’t passing a “jsonp” type specifier to your $.get, so it was using an ordinary XMLHttpRequest. However, your browser supported CORS (Cross-Origin Resource Sharing) to allow cross-domain XMLHttpRequest if the server OKed it. That’s where the Access-Control-Allow-Origin header came in. I … Read more
It’s actually not too complicated… Say you’re on domain example.com, and you want to make a request to domain example.net. To do so, you need to cross domain boundaries, a no-no in most of browserland. The one item that bypasses this limitation is <script> tags. When you use a script tag, the domain limitation is … Read more