Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’d like some advice on how to detect a “bad” URL before issuing an NSURLConnection call. By bad, I mean a non-existent host (e.g., http://www.no_such_host.com). I would need to first parse the URL to get just the host (suggestions welcome!) and then would like to see if the host actually is registered.
Is there a simple approach to using the DNS Resolver lookup, available in the iOS libraries?
If I were you, I would just go with the connection, then just catch in
NSURLConnectionDelegate‘s– connection:didFailWithError:method the error.NSURLConnectionwill still go to resolve the URL that you enter. The errors thatNSURLConnectionwill throw can be found in the Foundation Constants Reference (look forNSURLErrorDomain). If I remember correctly, the error that will be thrown isNSURLErrorCannotFindHost.