5

I am successfully using the rather awesome connection:didReceiveAuthenticationChallenge: delegate method of NSURLConnectionDelegate. Cool.

I want to properly support letting the user cancel out of an authentication challenge. So, the GUI I present to the user has a cancel button and the question is what behavior should happen behind that button.

Currently I do this [[challenge sender] cancelAuthenticationChallenge:challenge] and I have implemented the NSURLConnectionDelegate method connection:didCancelAuthenticationChallenge:. In the Apple docs I noticed this rather ambiguous note for this callback:

Available as part of an informal protocol prior to iOS 5.0.

Huh? The callback method that actually fires is connection:didFailWithError:

Can someone please shed some light here?

dugla
  • 12,774
  • 26
  • 88
  • 136

1 Answers1

4

Available as part of an informal protocol prior to iOS 5.0.

This just means that the delegate method in question wasn't part of a formal protocol, i.e. one declared using the @protocol directive. The methods in an informal protocol are usually documented along with the class that would call them.

The callback method that actually fires is connection:didFailWithError:

Both -connection:didCancelAuthenticationChallenge: and -connection:didFailWithError: have the same note about being part of an informal protocol prior to iOS 5.0. It sounds like your connection is failing to load the data, not being cancelled. You'd probably get the former message if you cancelled the challenge by calling:

[[challenge sender] cancelAuthenticationChallenge:challenge];

as described in Canceling the Connection.

Caleb
  • 124,013
  • 19
  • 183
  • 272
  • Caleb - actually there is a bug in my question I am in fact calling [[challenge sender] cancelAuthenticationChallenge:challenge]. That's the weird thing here. It is as if this method is a no-op. It doesn't appear to do anything at all. – dugla May 04 '12 at 23:29
  • I just fixed the bug in my question. – dugla May 04 '12 at 23:30