I searched a bit more on this and it seems that when using the XMLHttpRequest-based client (ajax) on Android phones (via the native browser) the runtime sends first an OPTIONS request (preflight request) to the remote side before it will allow any GET or POST requests. Anyone knows how to avoid this?
If not - what would be a standard way to run ajax or javascript on Android as clients? Can it be down via webview? Thanks On Oct 28, 12:32 am, kypriakos <demet...@ece.neu.edu> wrote: > I found some info on this from older threads - some mention of the > fact that > I call the page using file:// and also that the native browser in > Android does > not support cross-browser capabilities. Are these documented anywhere > or at least information on how Android deals with ajax/javascript? > > Thanks again > > On Oct 6, 11:06 am, kypriakos <demet...@ece.neu.edu> wrote:> Hi Doug, > > > thanks for the response. I am using 2.1. It's not that the browser > > does > > not handle ajax/js scripts but it seems that the HTTP headers that > > are emitted are not complete (as I listed above) ... is there a > > difference in how this object and HTTP is handled (and documented > > anywhere) > > by these browsers and how standard browsers do it (as you mentioned > > Chrome and > > Safari)? I didn't think so. > > > Thanks > > > On Oct 5, 2:55 pm, Doug <beafd...@gmail.com> wrote:> What version of > > Android are you using? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
