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?

Reply via email to