[Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.
Thiago Macieira
thiago.macieira at intel.com
Wed Sep 3 21:25:07 CEST 2014
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 OPTIONS / to example.com.
>
> Ok. Does that mean that from qml call should be like the following?
> x.open("OPTIONS", "http://example.com/"); // for request with url
> x.open("OPTIONS", "http://example.com"); // for request with asterisk
You tell me. How does it work right now in QML for a GET? How does it work in
HTML for a GET or for OPTIONS?
> >> How "OPTIONS *" call should be represented in QML? Should it be something
> >> like this:
> >> var x = new XMLHttpRequest;
> >> x.open("OPTIONS", url); // for request with url
> >> var x = new XMLHttpRequest;
> >> x.open("OPTIONS *", url); // for request with asterisk
> >
> > 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 for years. How do they do
this?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list