I don't have the reference handy, but I think there is an accept header needed for cors as well.
---
Here, I haven't tried cross origin requests with agk, but I have with a web server and a CEF application. I've got this on the server api request/response handler:
"Acess-Control-Allow-Origin", "*"
"Access-Control-Allow-Headers", "Cache-Control, Pragma, Origin, Authorization, Content-Type, X-Requested-With"
"Access-Control-Allow-Methods", "GET, PUT, POST"
And my client requests include:
delete header: "X-Requested-With"
add header: "dataType", "jsonp"
here is the kicker though, that I'm not sure what the agk equivalent would be, or if agk even needs to configure anything similar:
the client uses an http library to send the request, it needs this line of configuration:
$httpProvider.defaults.useXDomain = true;
http://games.joshkirklin.com/sulium
A single player RPG featuring a branching, player driven storyline of meaningful choices and multiple endings alongside challenging active combat and intelligent AI.