On Friday 12 September 2014 01:19:30 Valery Kotov wrote:
> Greetings everybody! Thank you for your responses.
>
> > Given the previous discussions referenced from the working groups for
>
> xmlhttprequest I think it's pretty clear that we can forget about OPTIONS
> *. Just using a
>
> > custom v
Greetings everybody! Thank you for your responses.
> Given the previous discussions referenced from the working groups for
xmlhttprequest I think it's pretty clear that we can forget about OPTIONS
*. Just using a
> custom verb and implementing it in the xmlhttprequest implementation of
qml seems l
On 10 September 2014 21:15, Thiago Macieira
wrote:
> On Tuesday 09 September 2014 18:24:58 Валерий Котов wrote:
> > I realize that we had this discussion before. But I have to ask. =)
> > Does not it make sense to add method and type in Operations enum for
> > options in case we need some special
On Tuesday 09 September 2014 18:24:58 Валерий Котов wrote:
> I realize that we had this discussion before. But I have to ask. =)
> Does not it make sense to add method and type in Operations enum for
> options in case we need some special treatment for "OPTIONS" verb?
Only if we have a method for
2014-09-07 21:16 GMT+03:00 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 s
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
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
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.
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
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 see links
> below for more details:
> http://www.
2014-09-04 12:44 GMT+03:00 Richard Moore :
> On 4 September 2014 10:29, Allan Sandfeld Jensen wrote:
>
>> On Thursday 04 September 2014, Richard Moore wrote:
>> > On 3 September 2014 20:25, Thiago Macieira
>> >
>> > wrote:
>> > > > > How is it represented in HTML5?
>> > > > > Just do it the same
On 4 September 2014 10:29, Allan Sandfeld Jensen wrote:
> On Thursday 04 September 2014, Richard Moore wrote:
> > On 3 September 2014 20:25, Thiago Macieira
> >
> > wrote:
> > > > > How is it represented in HTML5?
> > > > > Just do it the same way.
> > > >
> > > > I'm a little unsure that I unde
On Thursday 04 September 2014, Richard Moore wrote:
> On 3 September 2014 20:25, Thiago Macieira
>
> wrote:
> > > > How is it represented in HTML5?
> > > > Just do it the same way.
> > >
> > > I'm a little unsure that I understood. Could you please clarify what
> > > did you mean by "represented
On 3 September 2014 20:25, Thiago Macieira
wrote:
> > > How is it represented in HTML5?
> > > Just do it the same way.
> >
> > I'm a little unsure that I understood. Could you please clarify what did
> > you mean by "represented in HTML5"?
>
> XMLHttpRequests have existed in JavaScript and HTML5
On Wednesday 03 September 2014 20:31:04 Валерий Котов wrote:
> > Actually, I'm going back on what I had said. I think we can do
> > sendCustomRequest for both types of requests. The difference would be that
> > http://example.com sends OPTIONS * to example.com, but http://example.com/
> > sends OPT
2014-09-03 20:10 GMT+03:00 Thiago Macieira :
On Wednesday 03 September 2014 20:05:20 Валерий Котов wrote:
> >Greetings everybody!
>>
>> I'm working on QTBUG-35892 (
> >https://bugreports.qt-project.org/browse/QTBUG-35892) feature request:
> >adding support for HTTP OPTIONS method for QML XmlHttpReq
On Wednesday 03 September 2014 20:05:20 Валерий Котов wrote:
> Greetings everybody!
>
> I'm working on QTBUG-35892 (
> https://bugreports.qt-project.org/browse/QTBUG-35892) feature request:
> adding support for HTTP OPTIONS method for QML XmlHttpRequest class.
>
> >From discussion with Richard Mo
Greetings everybody!
I'm working on QTBUG-35892 (
https://bugreports.qt-project.org/browse/QTBUG-35892) feature request:
adding support for HTTP OPTIONS method for QML XmlHttpRequest class.
>From discussion with Richard Moore and Thiago Macieira I understood that 2
methods should be added to QNetw
18 matches
Mail list logo
