NSURLConnection+BlocksKit problem with HTTPS on iOS 5

[bwhiteley]

When starting several HTTPS connections simultaneously, the first two or three will succeed, and the rest will fail with connection timeout errors.

This only happens with HTTPS and iOS 5. The problem does not happen with HTTPS on iOS 4, or with HTTP on iOS 5.

The behavior is the same whether I use the iOS simulator and connect to a server on the local LAN, or if I use a device and connect to a server across the Internet.

[zwaldowski]

I expected this would happen. iOS 5 now has a formal protocol for
NSURLConnection, and implements new methods as well. Make sure you're
implementing all the new authentication methods in iOS 5. It may still
be a BlocksKit problem, but make sure
first.

[bwhiteley]

I did have the new authentication delegate method implemented, but it had a problem.

Here is a patch to restore the default behavior if a delegate doesn't implement the new method:

--- NSURLConnection+BlocksKit.m.orig 2011-12-15 14:12:26.000000000 -0700
+++ NSURLConnection+BlocksKit.m 2011-12-15 13:57:12.000000000 -0700
@@ -42,6 +42,8 @@
 - (void)connection:(NSURLConnection *)connection willSendRequestForAuthenticationChallenge:(NSURLAuthenticationChallenge *)challenge {
     if (connection.delegate && [connection.delegate respondsToSelector:@selector(connection:willSendRequestForAuthenticationChallenge:)])
         [connection.delegate connection:connection willSendRequestForAuthenticationChallenge:challenge];
+    else 
+        [challenge.sender performDefaultHandlingForAuthenticationChallenge:challenge]; 
 }