I think this is a webkit thing, since Android has the same problem. We have some authorization code, but I'm pretty certain that it doesn't do the right thing. That being said, I have no idea what the right thing is.
On Thu, May 2, 2013 at 4:52 PM, Shazron <[email protected]> wrote: > To summarize, this is an iOS thing, not a Cordova thing. We are just trying > to work around it. > > JIRA issue: > https://issues.apache.org/jira/browse/CB-2415 > > The proposed workaround is intrusive in that we basically need to create > our own NSURLConnection for each shouldStartLoadRequest call, and handle > the authentication challenge by letting it proceed (thus the call does not > "hang"). > > I'm not sure of the impact of this, but it touches every call. > > The only workaround in JavaScript is to do a setTimeout for the call, but > then we never get a 401 status code of course. > > Thoughts?
