On Mar 5, 2012, at 3:13 PM, Mike Abdullah wrote:
>
> On 5 Mar 2012, at 19:21, Alex Zavatone wrote:
>
>> I just found out why some JSON parsing was failing, the data returned from
>> the NSURLRequest was the HTML for our firewall authentication page.
>
> You mean NSURLConnection right? URL req
On Mar 5, 2012, at 11:21 AM, Alex Zavatone wrote:
> I just found out why some JSON parsing was failing, the data returned from
> the NSURLRequest was the HTML for our firewall authentication page.
Well that sucks. I believe a more correct response would have been 407Proxy
Authentication Requir
Yeah, at this facility, I get a web page asking to log in with auth parameters,
so it's going to be interesting.
Using the simulator, even if I enter the auth parameters in Safari, I'll run
the app again from Xcode and get the same HTML telling me that permission was
denied and asking for auth
I think generally a firewall ought to return an http status code of 302
redirected which you could probably key off for a login handler.
Time Dwarf,
Roaring Guy
On 2012-03-05, at 11:21 AM, Alex Zavatone wrote:
> I just found out why some JSON parsing was failing, the data returned from
> the
On 5 Mar 2012, at 19:21, Alex Zavatone wrote:
> I just found out why some JSON parsing was failing, the data returned from
> the NSURLRequest was the HTML for our firewall authentication page.
You mean NSURLConnection right? URL requests themselves are purely data
objects, they don't do any ne
I just found out why some JSON parsing was failing, the data returned from the
NSURLRequest was the HTML for our firewall authentication page.
Is there an established practice or set of documents on the iOS Dev Lib that
shows how to handle this? I scanned the sample code and found nothing.
Se
