On Fri, Apr 29, 2011 at 10:54, dabd <[email protected]> wrote:
> It is weird that despite POST not being allowed for cross domain requests
> (as
> you explained) and the timeout message, the server receives my request and
> processes it normally.
> I tried changing to a GET request and I get exactly the same behavior.
>
I think the selection of transport is made independent of POST vs GET
selection, although I'd have to look at the code to confirm that.
If you can send me the dumps of network traffic between the client and
server, I can tell you more specifically what's going on. I still suspect
that the client is expecting a JSONP-like response, for the Script
transport, and not getting it, so the callback is never being called, so the
request is timing out. The response from your server, to a cross-domain,
Script-transport request, MUST include a function call in the response. See
the documentation (maybe in qx.io.remote's documentation) for details.
Derrell
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
