Hi,
I don't know _exactly_ the reason for this, but I have a kind of "fix".
Whenever I remove the port-part (8124) from the URL it works.
So this:
var req = new qx.io.remote.Request(
"http://127.0.0.1";,
"POST",
"application/json");
req.send();
issues a POST (according to FireBug).
/Peter
On 2010-06-16 09:39 b a wrote:
> Hi Ilkka,
>
> On 6/15/10, Ilkka Oksanen <[email protected]> wrote:
>> Hi,
>>
>> On Tue, Jun 15, 2010 at 3:21 PM, b a <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> I started writing something with qooxdoo and I also wrote a server
>>> so that the qooxdoo app communicates with that.
>>>
>>> In qooxdoo I made a POST request like this
>>>
>>> var req = new qx.io.remote.Request(
>>> "http://127.0.0.1:8124";,
>>> "POST",
>>> "application/json");
>>>
>>> And in the server I printed all Request methods of incoming requests.
>>> I expected to get a "POST" request on the server, but in *reality* ... I
>>> got
>>> an "OPTIONS" request.
>>>
>>>
>> That OPTIONS request is not related to Qooxdoo. Some browser use it to learn
>> the additional features that the web server supports. OPTIONS is part of the
>> HTTP standard.
>>
>> You can safely configure your server app to respond "HTTP/1.1. 501 Not
>> implement" to such requests. In fact 501 should be the default answer to all
>> unknown requests.
>
> I'm afraid I cannot do that since I was expecting a POST and not
> OPTIONS on serverside.
> Also, I intend to take data from the POST request and provide a
> response to the client.
> But your 501 suggestions is interesting and may be useful, only not in my
> case.
>
> Thank you
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
