$http cache doesn't work for JSONP requests

[tcoopman]

Using the $http with cache doesn't work for JSONP methods. At the moment the cache only works for GET methods, while I think it could be useful to cache JSONP too if the the cache-control headers allow it.

Are there reasons JSONP can't be cached? I think the callback could be a small issue?

• example of the problem: http://plnkr.co/edit/EG7yiZo3poTzxeMOfcUp
• Link to the discussion on G+: https://plus.google.com/u/0/109624499308077610663/posts/H2N7YsRi9CU

After some more research I've found this discussion on the mailinglist and merge request that is looks like it could solve this issue. At the moment the merge request is closed though.

• https://groups.google.com/forum/?fromgroups=#!searchin/angular/$24http$20cache$20jsonp/angular/p9WbhHik31I/aTo9EBYSmbwJ
• JSONP requests with the same callback name #1548

[jendib]

I have the same question here, why JSONP is not cached?
It's not a technical problem, because if we comment out the part checking if it's a GET request, JSONP caching works.

[iamjohnlong]

I was wondering the same.

[Guuz]

👍

[steveruiz]

It looks like the problem has to do with the way URL's are constructed for JSONP requests. Angular replaces the JSON_CALLBACK parameter value on each request so the URL is unique each time. This URL mismatch causes the cache to miss.

[cironunes]

this one is related #3073

[maxbates]

+1

[mrpollo]

👍 great catch