On 17 mai, 20:33, Seven Corners <[email protected]> wrote: > I'm finding a strange situation where an HTTP GET gets changed to > OPTIONS, and I receive nothing from my GET. I'm working on an > application where I'll be working with various CRUD operations via > REST calls to my local server. Right now I'm just writing the GET and > finding that my response has no data and a status of 0. I learn from > the log that the GET has been changed to HTTP OPTIONS. Any clue why, > and what I can do to fix it?
http://www.w3.org/TR/cors/#cross-origin-request-with-preflight0 > I think what I need to do is a common > and straightforward thing; surely other people have run into this? With most browsers until last year, it would have failed, because of the "same origin policy". Nowadays, all "modern" browsers (with the notable exception of IE) implement CORS, but older versions still don't. (t should be noted that IE8 supports CORS but you have to use a special XDomainRequest instead of XMLHttpRequest, and GWT isn't designed with cross-origin requests in view so it won't use XDomainRequest) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
