Validating response #64
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 28, 2014 15:15
|
I had a similar issue (getting 403 from the server) and this fixed it. So, thanks @beniciojunior 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm using
AFDownloadRequestOperationon my project, but when it receives 416 HTTP status (Requested Range Not Satisfiable), the success block is being called. So I created this fix: every time responseObject is accessed, it validates the response using the (default)responseSerializer, which checks acceptable HTTP status codes.Adding to that, I removed
+ acceptableStatusCodesmethod that is not called on AFNetworking 2.0.I hope this helps.