Skip to content
This repository was archived by the owner on Jan 17, 2023. It is now read-only.

Clarify documentation for supported encodings in AFJSONResponseSerializer #3750

Merged
merged 3 commits into from
Nov 24, 2017
Merged

Clarify documentation for supported encodings in AFJSONResponseSerializer #3750

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
84e409d
Clarify documentation for supported encodings in AFJSONResponseSerial…
skyline75489 Oct 13, 2016
9fbf003
Update content to reflect the newer RFC
skyline75489 Oct 14, 2016
8ad7050
Fix typo
skyline75489 Jul 13, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions AFNetworking/AFURLResponseSerialization.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,8 @@ NS_ASSUME_NONNULL_BEGIN
- `application/json`
- `text/json`
- `text/javascript`

In RFC 7159 - Section 8.1, it states that JSON text is required to be encoded in UTF-8, UTF-16, or UTF-32, and the default encoding is UTF-8. NSJSONSerialization provides support for all the encodings listed in the specification, and recommends UTF-8 for efficiency. Using an unsupported encoding will result in serialization error. See the `NSJSONSerialization` documentation for more details.
*/
@interface AFJSONResponseSerializer : AFHTTPResponseSerializer

Expand Down