-
Notifications
You must be signed in to change notification settings - Fork 3
Exception handling #2
Comments
You'll just need to check RFResponse's error property: /*!
This property will contain the NSError in case something goes wrong. /*!
basically you'd do something like [RFService execRequest:r completion:^(RFResponse *response) { |
I'll update the README file with some examples and close this issue when I do... |
Great, Thank you. |
Just want to confirm, it's working! |
Yeah, just use additionalHTTPHeaders property of RFRequest. /*!
Just add key-value pairs to a NSDictionary and assign to this property. |
Can you post some examples how to handle exceptions?
let say you do
[RFService execRequest:r completion:^(RFResponse *response) {
but server is not available or the document is not found (404)
The text was updated successfully, but these errors were encountered: