[Proto-Scripty] Re: Chrome 5 refused to get unsafe header xjson

2010-09-17 Thread nigeke...@googlemail.com
I think I'm being caught out by the SOP. My app is a phonegap app and so it's domain is the client machine so to speak. When I try to talk to the server from the client Chrome enforces the SOP. The status of the transport object is 0 in Chrome debugger. I'm looking at jsonp solutions. My

Re: [Proto-Scripty] Re: Chrome 5 refused to get unsafe header xjson

2010-09-16 Thread Richard Quadling
On 16 September 2010 11:21, nigeke...@googlemail.com nigeke...@googlemail.com wrote: Content-Type: application/json; That's the important bit. So, now your JSON data will be in ... transport.responseJSON You don't need to evalJS() as JSON is JS. -- Richard Quadling Twitter : EE : Zend

[Proto-Scripty] Re: Chrome 5 refused to get unsafe header xjson

2010-09-16 Thread nigeke...@googlemail.com
Still not working in Chrome. Still getting the same error. I tried with transport.responseJSON and transport.headerJSON. The only positive difference is that the rails webrick server now shows the request going to the correct controller and it executes the query. It was not doing this before.

[Proto-Scripty] Re: Chrome 5 refused to get unsafe header xjson

2010-09-15 Thread nigeke...@googlemail.com
Thanks for response Richard. Not sure exactly what you mean. The response from the server when I key in the url directly to chrome is a json array/hash of previously entered data: [{post: