Hi Mig,

the cross-domain-policy is enforced by the browser, so there is basically 
nothing you can do about it other than using cross-domain compatible 
transports. Can you solve your problem when setting cross domain to true?

Maybe one alternative is to use HTTP Access control [1], but this requires 
configuration on the server-side and is limited to modern browsers.

Regards
Tristan

[1] https://developer.mozilla.org/En/HTTP_access_control

Am 15.11.2010 um 14:33 schrieb Mig:


Hi Tristan,

first of, thanks for the very fast response. Yes if origin and target-domain
are the same, it works. But in fact I'm trying to do cross-domain requests.

I got a server running that responses on HTTP-GET requests. And the iframe
catches that successfully! But now I can't get the responses out of there.
Shure, I could go make qx.io.remote.Request with cross domain (true), but
this causes such a big header wich i was trying to prevent.

Best Regards,
Mig

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to