Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-07 Thread Thiago Macieira
On Sunday 07 September 2014 11:13:59 Thiago Macieira wrote: > On Sunday 07 September 2014 09:05:43 Thiago Macieira wrote: > > On Sunday 07 September 2014 15:22:09 Валерий Котов wrote: > > > If yes, how should it be performed? It is possible to send "OPTIONS" > > > request by using sendCustomRequest

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-07 Thread Thiago Macieira
On Sunday 07 September 2014 09:05:43 Thiago Macieira wrote: > On Sunday 07 September 2014 15:22:09 Валерий Котов wrote: > > If yes, how should it be performed? It is possible to send "OPTIONS" > > request by using sendCustomRequest. But how should user perform "OPTIONS > > *" > > request? Should it

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-07 Thread Thiago Macieira
On Sunday 07 September 2014 15:22:09 Валерий Котов wrote: > If yes, how should it be performed? It is possible to send "OPTIONS" > request by using sendCustomRequest. But how should user perform "OPTIONS *" > request? Should it depend on url? I recommend you send OPTIONS * if the URL has no path.

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-07 Thread Валерий Котов
2014-09-06 20:03 GMT+03:00 Jeremy Lainé : > On 09/06/2014 01:19 PM, Валерий Котов wrote: > > There is one more thing. Should we care about cross-origin resource > sharing protocol? If I got it right, XMLHttpeRequset should perform > "OPTIONS" preflight request before real cors request. Please se