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 … Read more
You could simply ignore the invalid certificate if you are not sending any sensitive information. This article describes how you could do that. Here is an example implementation by Alexandre Colucci for one of the methods described in that article. Essentially you want to define a dummy interface just above the @implementation: @interface NSURLRequest (DummyInterface) … Read more
There’s a thread on Apple dev forums discussing this issue. Apparently on iPhone OS, the setter mandates timeoutInterval a minimum of 240 seconds (4 minutes). This only occurs when the postBody is not empty (typically when using a POST request). This seems crazy, but apparently it’s there to make sure requests leave the system even … Read more
I recommend you to see WWDC Sessions about network application in iPhone OS. WWDC 2010 Session 207 – Network Apps for iPhone OS, Part 1 WWDC 2010 Session 208 – Network Apps for iPhone OS, Part 2 The lecturer said “Threads Are Evil™” for network programming and recommended to use asynchronous network programming with RunLoop. … Read more
The expected content length is only set when the server provides it, such as by a Content-Length response header. A -1 size means the expected content size is unknown. If you set Accept-Encoding: gzip on your request, the URL loading system will fib and tell you the expected size is -1, no matter what Content-Length … Read more
There’s lots of ways you can do this depending on the behavior you want. You can send a bunch of asynchronous requests at once, track the number of requests that have been completed, and do something once they’re all done: NSInteger outstandingRequests = [requestsArray count]; for (NSURLRequest *request in requestsArray) { [NSURLConnection sendAsynchronousRequest:request queue:[NSOperationQueue mainQueue] … Read more
According to a post on the Apple developer forum, the minimum timeout interval for POST is 240 seconds. Any timeout interval shorter than that is ignored. If you require a shorter timeout interval, use an async request along with a timer and call cancel on the NSURLConnection as needed. link to thread: here
Your data is wrong. If you expect the data to be found in the $_POST array of PHP, it should look like this: const char *bytes = “mydata=Hello%20World”; If you want to send XML Data, you need to set a different HTTP Content Type. E.g. you might set application/xml; charset=utf-8 If you set no HTTP … Read more
you can use NSURLConnection class NSURLRequest *request = [NSURLRequest requestWithURL:[NSURL URLWithString:url]]; [[[NSURLConnection alloc] initWithRequest:request delegate:self] autorelease]; and handle its response and errors using its delegate methods. – (void)connection:(NSURLConnection *)connection didReceiveResponse:(NSURLResponse *)response – (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data – (void)connection:(NSURLConnection *)connection didFailWithError:(NSError *)error – (void)connectionDidFinishLoading:(NSURLConnection *)connection You can find implementation of NSURLConnection Apple docs: Using NSURLConnection How … Read more
I think you would be better off using the NSJSONSerialization class like this: NSDictionary *tmp = [[NSDictionary alloc] initWithObjectsAndKeys: email, @”Email”, fname, @”FirstName”, nil]; NSError *error; NSData *postdata = [NSJSONSerialization dataWithJSONObject:tmp options:0 error:&error]; [request setHTTPBody:postData]; Using a dictionary and then converting it to JSON it’s easier than creating it like a string. Good luck! [SWIFT … Read more