Issues - pokeb/asi-http-request

pokeb / asi-http-request

452

Description:

Easy to use CFNetwork wrapper for HTTP requests, Objective-C, Mac OS X and iPhone

Sort by: Priority | Votes | Last Updated

Loading…

6.

0 votes

iPhone 3.1 and FileUpload
1 comment Created 2 months ago by haligasd

Title

Body
Been using the File upload for quite some time and every since 3.1 came out on the iPhone I get the error "Domain=ASIHTTPRequestErrorDomain Code = 1 UserInfo == xxxx 'A connection failure occurred: SSL problem (possibly a bad/expired/self-signed certificate)'" Our hosting provider assures us all is good on the cert/config areas. This is totally random and when I am good 3G coverage. I can immediately retry and it may or may not work. Not sure if this is an issue in the ASI code just wanted to toss it out there in case anyone else is having this.
or cancel

Been using the File upload for quite some time and every since 3.1 came out on the iPhone I get the error "Domain=ASIHTTPRequestErrorDomain Code = 1 UserInfo == xxxx 'A connection failure occurred: SSL problem (possibly a bad/expired/self-signed certificate)'"

Our hosting provider assures us all is good on the cert/config areas.

This is totally random and when I am good 3G coverage. I can immediately retry and it may or may not work. Not sure if this is an issue in the ASI code just wanted to toss it out there in case anyone else is having this.

Comments

pokeb Wed Sep 30 08:19:12 -0700 2009 | link

Hi

Sorry for the delay in getting back to you on this, I've been away for a couple of weeks.

Hmm, that does sound like a curious issue. If you have any 3.0 or 2.2.1 devices, can you see this issue? Does it make any difference if you set validatesSecureCertificate to NO? (I don't recommend you do this in shipping apps)

I guess it's possible that a bug has crept in somewhere which is causing this error to be erroneously triggered, perhaps the release of the problem ASIHTTPRequest code coincided with the 3.1 release. Are you using the latest version of ASIHTTPRequest?

It would be helpful if you could drop me details on the url(s) you're seeing this problem with - ben@allseeing-i.com.

Thanks

Ben

Comment
Hi Sorry for the delay in getting back to you on this, I've been away for a couple of weeks. Hmm, that does sound like a curious issue. If you have any 3.0 or 2.2.1 devices, can you see this issue? Does it make any difference if you set validatesSecureCertificate to NO? (I don't recommend you do this in shipping apps) I guess it's possible that a bug has crept in somewhere which is causing this error to be erroneously triggered, perhaps the release of the problem ASIHTTPRequest code coincided with the 3.1 release. Are you using the latest version of ASIHTTPRequest? It would be helpful if you could drop me details on the url(s) you're seeing this problem with - ben@allseeing-i.com. Thanks Ben
or cancel

Parsed with GitHub Flavored Markdown
13.

0 votes

Refactor progress tracking code
0 comments Created 6 days ago by pokeb

Title

Body
Progress tracking code feels messy and contains lots of repetition. [lhunath's fork](http://github.com/lhunath/asi-http-request/commit/d28fe4062bc2bb665e3d5828e2266584800f30d2) has moved the queue progress methods into a protocol, it would be worth looking at this too.
or cancel

Progress tracking code feels messy and contains lots of repetition.

lhunath's fork has moved the queue progress methods into a protocol, it would be worth looking at this too.

Comments

Parsed with GitHub Flavored Markdown

Labels

iPhone 3.1 and FileUpload

Comments

Refactor progress tracking code

Comments