On Sun, Jul 27, 2008 at 8:03 PM, Dennis Davydenko <[EMAIL PROTECTED]> wrote: >> >> Hi guys! >> >> I'm kinda new to Cocoa framework. I'm trying to create an application that >> will send requests to my web server. Everything is cool, except error >> handling. I would assume that any error while request is being sent should >> trigger didFailWithError, but it seems it is not what happening. Instead I >> got connectionDidFinishLoading and no errors. I tried to use >> didReceiveResponse and extract statusCode of response - that worked, but if >> I want to handle all possible HTTP error statuses (like 401, 403, 404, 500 >> and so on) I will have to create all this handling on my own... I think I'm >> missing something here - there should be some classes that are implemented >> to perform this job... or I'm too naive? >> >> Any advices are appreciated!
While those could be considered HTTP errors, they are not connection errors. didFailWithError: is for things like connection refused, connection reset, etc. If you get a 404, the HTTP connection did not encounter any error. It received a 404 status code (which is legitimate), and some data in response to its request. What you do with that code/data is then up to you. So it all depends on what you want your error handler to do. Figure that out, then write some code to do it. As an HTTP client you will need to know what codes are "good" and what codes are "bad", that's just how it is. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
