iOS: How can i receive HTTP 401 instead of -1012 NSURLErrorUserCancelledAuthentication iOS: How can i receive HTTP 401 instead of -1012 NSURLErrorUserCancelledAuthentication ios ios

iOS: How can i receive HTTP 401 instead of -1012 NSURLErrorUserCancelledAuthentication


Yes. Stop using the synchronous API. If you use the asynchronous delegate-based API then you have a lot more control over the connection. With this API, except in cases where an error is encountered before the HTTP header is received, you will always receive -connection:didReceiveResponse:, which gives you access to the HTTP header fields (encapsulated in an NSURLResponse object). You can also implement authentication using the relevant delegate methods if you are so inclined.


Workaround:

[NSURLConnection sendAsynchronousRequest:request queue:[NSOperationQueue new] completionHandler:^(NSURLResponse *response, NSData *data, NSError *connectionError) {NSHTTPURLResponse *aResponse = (NSHTTPURLResponse *)response;int statusCodeResponse = aResponse.statusCode;NSString *strError = [NSString stringWithFormat:@"%@", [connectionError description]];if ([strError rangeOfString:@"Code=-1012"].location != NSNotFound) {    statusCodeResponse = 401;   }

Is not the best solution, but it works!


I'm surprised at the "recommended" answer to this thread.

Fine, I'm sure using the async version methods are better, but it still doesn't explain why the sendSynchronousRequest function does let you pass in a variable to return the response code, but in some circumstances, it just returns nil.

It' 4 years since this issue was reported, I'm using XCode 6.2 with iOS 8.2, and this ancient bug is still present.

My web services deliberately return a 401 error when a user's username & password aren't correct.

When my iPhone app calls this service (with the wrong credentials)...

NSHTTPURLResponse *response = nil;NSData *data = [ NSURLConnection sendSynchronousRequest:request returningResponse:&response error:&error ];

..response is returned as nil (so I can't test for the HTTP Response 401), error receives a -1012 message wrapped up like this:

    Error Domain=NSURLErrorDomain Code=-1012 "The operation couldn’t be completed. (NSURLErrorDomain error -1012.)"     UserInfo=0x174869940 {NSErrorFailingURLStringKey=https://mywebservice.com/Service1.svc/getGroupInfo/6079, NSUnderlyingError=0x174e46030     "The operation couldn’t be completed. (kCFErrorDomainCFNetwork error -1012.)",NSErrorFailingURLKey=https://mywebservice.com/Service1.svc/getGroupInfo/6079}

and the sendSynchronousRequest function returns a lengthy XML string containing... well... this...

<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml">  <head>    <title>Request Error</title>    <style>BODY { color: #000000; background-color: white; font-family: Verdana; margin-left: 0px; margin-top: 0px; } #content { margin-left: 30px; font-size: .70em; padding-bottom: 2em; } A:link { color: #336699; font-weight: bold; text-decoration: underline; } A:visited { color: #6699cc; font-weight: bold; text-decoration: underline; } A:active { color: #336699; font-weight: bold; text-decoration: underline; } .heading1 { background-color: #003366; border-bottom: #336699 6px solid; color: #ffffff; font-family: Tahoma; font-size: 26px; font-weight: normal;margin: 0em 0em 10px -20px; padding-bottom: 8px; padding-left: 30px;padding-top: 16px;} pre { font-size:small; background-color: #e5e5cc; padding: 5px; font-family: Courier New; margin-top: 0px; border: 1px #f0f0e0 solid; white-space: pre-wrap; white-space: -pre-wrap; word-wrap: break-word; } table { border-collapse: collapse; border-spacing: 0px; font-family: Verdana;} table th { border-right: 2px white solid; border-bottom: 2px white solid; font-weight: bold; background-color: #cecf9c;} table td { border-right: 2px white solid; border-bottom: 2px white solid; background-color: #e5e5cc;}</style>  </head>  <body>    <div id="content">      <p class="heading1">Request Error</p>      <p>The server encountered an error processing the request. The exception message is 'Access is denied.'. See server logs for more details. The exception stack trace is: </p>      <p>   at System.ServiceModel.Dispatcher.AuthorizationBehavior.Authorize(MessageRpc& rpc)   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</p>    </div>  </body></html>

Come on Apple, fix your bugs...


matomo