cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zach White <whit1...@gmail.com>
Subject Re: [iOS] XmlHttpRequest and 401 Unauthorized
Date Fri, 03 May 2013 13:52:32 GMT
Unless something has changed since I last looked, I thought the Android
issue was resolved: https://issues.apache.org/jira/browse/CB-2284.


On Thu, May 2, 2013 at 8:28 PM, Jesse <purplecabbage@gmail.com> wrote:

> Not just iOS + Android ... https://issues.apache.org/jira/browse/CB-2428
>
>
> @purplecabbage
> risingj.com
>
>
> On Thu, May 2, 2013 at 4:56 PM, Joe Bowser <bowserj@gmail.com> wrote:
>
> > Applicable Android counterpart:
> > https://issues.apache.org/jira/browse/CB-2962
> >
> > On Thu, May 2, 2013 at 4:54 PM, Joe Bowser <bowserj@gmail.com> wrote:
> > > 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 <shazron@gmail.com> 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?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message