Currently the API does not pass the Access-Control-Allow-Origin header. This means that browsers can not make ajax requests to this domain (without turning off security features).

I don't think including this header would open up a security issue for the Linode API, as it simply allows browsers to hit the API without going through another server.

Any movement on this or reason it's being held up?

I'm curious what use case you have for needing to use the Linode API in this manner.

_________________
'If debugging is the process of removing bugs, then programming must be the process of putting them in.' //Edsger Dijkstra
'Nothing is withheld from us which we have conceived to do.' | 'Do things that have never been done.' //Russell Kirsch

What I originally wanted this for was to create an entirely in-browser management panel replacement for Linode. I didn't want to store the user's API key or pass requests through a server.

I've been told this is now available!



I guess progress has slowed at Linode to the point where it takes a year to implement something like this. Sad.

I'm excited to see folks can get what they wanted and still whine about it.

- Les

Had a big long drawn out response, deleted it. No use arguing with you. I'm happy Linode implemented a seemingly simple feature per my request. And I am sad it took this long, I didn't mean for it to come off as whining. But okay.