iOS Development: Why do I always get the “A connection failure occurred” on the 1st attempt, but success on the next?

Question

I\'m using the ASIHTTPRequest lib in my iOS app to make RESTful requests to my Rails 3 web app. I seeing a weird and somewhat consistent error the 1st time I try to make a

Answer 1

i also had to set response setHeader Connection to "close" in by Java servlet

response.setHeader("Connection", "close");

Answer 2

This issue I had a lot of hard time to figure out why. The problem resides in ASIHTTPRequest itself (iOS), not the rails code.

To make a long story short, the problem is specific to the use of persistent connection for every request sent by ASIHTTPRequest.

While this is good for GET requests, most server implementation does not allow persistent connection to be used with POST request.

I didn't really have time to investigate it deeply on the server side of things but I think that the problem resides with the 100-Continue header that should be sent (and which isn't) with request that has body attached to it (hence PUT/POST). If you want to have a deeper look at what I'm talking about go have a read at the spec sheet: http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html

So the persistent connection used by ASIHTTPRequest wait for a 100 response to be sent, which is never sent. so it ends up being timed out.

A fix is to set persistentConnection to NO with your post requests like the following:

ASIHTTPRequest *req                     = [ASIHTTPRequest requestWithURL:url];
req.shouldAttemptPersistentConnection   = NO;

Answer 3

On iOS 5.1, even after upgrading ASIHTTPRequest to ASIHTTPRequestVersion = @"v1.8.1-61 2011-09-19" still needed:

ASIHTTPRequest *req = [ASIHTTPRequest requestWithURL:url];
req.shouldAttemptPersistentConnection = NO;

Answer 4

Secure Connection Failed

      An error occurred during a connection to login.yahoo.com.

SSL received a record with an incorrect Message Authentication Code.

(Error code: ssl_error_bad_mac_read)

The page you are trying to view can not be shown because the authenticity of the received data could not be verified. Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.