後端介面統一採用 UTF-8 編碼,是現在多數專案的標準做法。但只要 iOS 端在組裝請求時少做一步編碼處理,中文欄位(例如使用者暱稱)送到伺服器再拉回來,往往就變成一堆問號或亂數。下面以「新增家庭成員」這個功能為例,把問題成因與解法完整走一遍。
使用者輸入的姓名是中文(例如「藍天」),其餘欄位包含年齡、生日、身高、體重與性別,同時還要上傳一張 PNG 頭像。程式碼大致如下:
NSString *childName = nameTextField.text; // 這裡輸入的是中文,例如:藍天
NSString *age = ageTextField.text;
NSString *birthday = self.birthdayTextField.text;
NSString *height = heightTextField.text;
NSString *weight = weightTextField.text;
NSString *sex = [NSString new];
if ([self.sexTextField.text isEqualToString:@"男"]) {
sex = @"1";
} else {
sex = @"0";
}
NSData *iconData = UIImagePNGRepresentation(self.memberIconView.image); // PNG 轉 NSData
/********* 先存到伺服器,由伺服器回傳一個 ID *********/
if ([self checkNetworkIsAnable]) {
request = [ASIFormDataRequest requestWithURL:[NSURL URLWithString:api_addChild]];
[request setPostFormat:ASIMultipartFormDataPostFormat];
[request setUseCookiePersistence:YES];
[request setPostValue:childName forKey:@"childnickname"];
[request setPostValue:age forKey:@"childage"];
[request setPostValue:birthday forKey:@"childbirthday"];
[request setPostValue:weight forKey:@"childweight"];
[request setPostValue:height forKey:@"childheight"];
[request setPostValue:sex forKey:@"childsex"];
[request setData:iconData withFileName:@"icon.png" andContentType:@"image/png" forKey:@"photo"];
[request setDelegate:self];
[request setDidFailSelector:@selector(requestFailed:)];
[request setDidFinishSelector:@selector(requestSuccess:)];
// [request startSynchronous]; // 同步請求
[request startAsynchronous]; // 非同步請求
}
伺服器回傳的是 JSON,解析流程本身沒有毛病,但把 member.name 印到畫面上時,中文永遠是亂碼:
- (void)requestMemberListFromServerSuccess:(ASIHTTPRequest *)request1 {
// 先清空圖片快取
[[SDImageCache sharedImageCache] clearDisk];
[[SDImageCache sharedImageCache] clearMemory];
NSData *data = [request1 responseData];
NSLog(@"requst ===%@", [request1 responseString]);
NSError *error;
NSArray *dic = [NSJSONSerialization JSONObjectWithData:data
options:NSJSONReadingAllowFragments
error:&error];
NSLog(@"getchildList dic == %@", dic);
if (error) {
NSLog(@"error===%@", error);
}
if (self.members) {
self.members = nil;
self.members = [NSMutableArray new];
}
NSMutableArray *array = [NSMutableArray array];
if (dic.count != 0) {
for (int i = 0; i < dic.count; i++) {
NSDictionary *memberDic = [dic objectAtIndex:i];
Member *member = [[Member alloc] init];
member.age = [memberDic objectForKey:kServerMemberAgeKey];
member.ID = [[memberDic objectForKey:kServerMemberIDKey] integerValue];
member.Weight = [memberDic objectForKey:kServerMemberWeightKey];
member.height = [memberDic objectForKey:kServerMemberHeightKey];
member.birthday = [memberDic objectForKey:kServerMemberBirthdayKey];
NSString *sexString = [memberDic objectForKey:kServerMemberSexKey];
if ([sexString integerValue] == 1) {
member.sex = @"男";
} else {
member.sex = @"女";
}
member.name = [memberDic objectForKey:kServerMemberNameKey]; // 這裡拿到亂碼
member.icon_urlString = [api_ServerPre stringByAppendingString:
[memberDic objectForKey:kServerMemberIconUrlKey]];
[array addObject:member];
}
}
}
關鍵在於「百分比編碼(Percent Encoding)」。中文在傳輸過程中若被中途轉碼,就會失真;先把中文轉成 %XX 形式的 ASCII 字串,可以讓它安全地穿過網路層,取回來再還原即可。
送出請求時,對中文欄位做一次 UTF-8 百分比編碼:
NSString *childName = [nameTextField.text stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding];
解析回傳資料時,對同一欄位做反向還原:
member.name = [[memberDic objectForKey:kServerMemberNameKey]
stringByReplacingPercentEscapesUsingEncoding:NSUTF8StringEncoding];
一去一回配對完成,中文亂碼的問題就解決了。
這種做法本質上是「約定式編碼」:客户端與伺服器必須對同一欄位採用一致的編碼策略,否則只會把亂碼換成另一種亂碼。若專案已經全面採用 NSURLSession 或 AFNetworking,系統 API 通常會自動處理 URL 編碼,就不必再手動呼叫這兩個方法。另外,這兩個 API 在 iOS 9 之後已被標記為廢棄,新專案建議改用 stringByAddingPercentEncodingWithAllowedCharacters:。
延伸閱讀:iOS 漢字轉碼