JSONP Callback function $http

[todiadiyatmo]

Hi i'am quite new in angular.

I'am triying to use the $http module for xhr request.

However, the callback name must be "JSONP_CALLBACK" in which angular will turn the callback name to callback=angular.callbacks._1

There's some web web service which cannot accept "angular.callbacks._1 "callback name, for example

http://dev.markitondemand.com/Api/Lookup/jsonp?input=GM&callback=callback=angular.callbacks._1

i solve this with a messy hack found on stackoverflow

http://jsfiddle.net/pMGgR/

[raghur]

me too - using the windows ACS service and it doesnt like the call back name

[pkozlowski-opensource]

@raghur @todiadiyatmo do you guys know what upsets your JSONP endpoints with the callback names generated by AngularJS? Is it a dot? Or underscore? Or sth else altogether?

Getting rid of a dot might be problematic since callbacks would have to be registered in a global (window) scope....

[mawo87]

I had the same problem with the TrustYou API. I suspect the dot being the issue ...
I also came across the hack on stackoverflow but I decided to use jQuery.getJSON in this particular case instead

[raghur]

@pkozlowski-opensource - In the Chrome network console, if I click on the url to ACS, I get an ACS error page that tells me that the callback name is invalid.

[patrickkettner]

@haraldringvold I would sugest opening a new issue if you are having one, otherwise stackexchange would be the best place to ask a more general question like this.

[dancras]

I'm having the same trouble with a third party API (all the dots being removed from the callback function name). Since my search brought me here I figure adding the following snippet here might be useful for others who find themselves in the same situation.

Add the following immediately before making a jsonp request.

var c = $window.angular.callbacks.counter.toString(36);

$window['angularcallbacks_' + c] = function (data) {
    $window.angular.callbacks['_' + c](data);
    delete $window['angularcallbacks_' + c];
};

The main problem is that this relies heavily on angular's current jsonp implementation and is likely to need maintenance in the future.

As a more permanent solution the framework could have a low level service purely for registering globals (heavily and uniquely prefixed so that multiple angular apps don't collide), which would also make cleaning up after an app much simpler.

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!

[wildavies]

I am getting the same issue on the CIneworld API, but I have used it without issue on other API's.
It definitely seems as though some web services can't accept a callback name in the format "angular.callbacks._1"

It happens whether I use $http.jsonp, $http.get or .get as part of a service with AngularJS 1.0.7 and also 1.0.8.

I can use jQuery instead or the alternative fix (http://stackoverflow.com/questions/13267285/angular-resource-with-jsonp-not-working), but it would be nice to use the full features of AngularJS.

[chrism2671]

I tested it with 1.0.8 & 1.2.0rc1 and have the same problem with both.

[rixrix]

This isn't working for me.

version: 1.0.8
OS: Mountain Lion

I did a JSONP request on one of the file hosted at Github, like so

$http.json("https://raw.github.com/<username>/<reponame>/master/somedata.json?callback=JSON_CALLBACK")

ATM, the work-around mentioned by @williamtdavies worked for me

cheers

[petebacondarwin]

Let's move this discussion to #3073

[TWiStErRob]

There's no point in merging this to #3073 because the problem caused by this bit:

'angular.callbacks.' + callbackId

which still exists in that pull request.
That is the dots will still be in callback=... and hence not all endpoints out there in the wild will work.
I'm using 1.2.4.

(I'd like to point out that I've watch/read a few tutorials and I was impressed with angular, until I wrote

$resource('http://...', { ..., callback: 'JSON_CALLBACK' }, ...);

as my 10th ever line of angular code, now I am really disappointed!)

[doneyourdamage]

This is also a problem for me.

"ReferenceError: JSONP_CALLBACK is not defined" on fully valid JSONP