incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Neveu (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-208) WP7 + JQuery call to $.ajax does not work
Date Fri, 03 Feb 2012 16:31:54 GMT


Alan Neveu commented on CB-208:

I figured this out. Turns out the requestHeaders from my custom proxy were not being honored
when PhoneGap hijacks the XHR. Using phonegap-1.4.0.js, I added this line of code:


just before line 3796, which is:

return this.wrappedXHR.send(data);

and that solved it.  Is there any way to craft the PhoneGap function so that it honors the
requestHeaders that are already specified on the XHR before it hi-jacks it?  That might be
a good solution.
> WP7 + JQuery call to $.ajax does not work
> -----------------------------------------
>                 Key: CB-208
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: WP7
>    Affects Versions: 1.4.0
>         Environment: VS.NET 2010, Using the latest code for the 1.4.0 release candidate,
plus a fairly simple custom $.ajax function.
>            Reporter: Alan Neveu
>            Assignee: Jesse MacFadyen
>             Fix For: 1.5.0
>         Attachments: json2.js
> My own $.ajax function works great all by itself, but with phonegap-1.4.0.js present
my $.ajax calls get hi-jacked and errors occur in that last function in phonegap-1.4.0.js.
 If I comment out that whole function, my $.ajax calls work just great.  I need my custom
$.ajax calls because they use some custom JSON code written by Rick Strahl that properly deals
with Microsoft formatted dates going in and out of ASMX web services that use JSON for serialization.
> It looks like the error is happening on the line that says:
> return this.wrappedXHR.send(data);
> Is there any way I can disable the hi-jacking of $.ajax calls without modifying phonegap-1.4.0.js?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message