_kCFStreamErrorCodeKey = -2102仅限某些ISP的wifi

Question

我使用下面的代码将文件发送到服务器:

NSString *urlString = [NSString stringWithFormat:@"%@%@",[LIUtility sharedUtility].uploadConnectionURL,BR_SERVER_UPLOAD_ADDRESS_FILE];

self.request =[[NSMutableURLRequest alloc] init];
[self.request setURL:[NSURL URLWithString:urlString]];
[self.request setHTTPMethod:@"POST"];

PKMultipartInputStream *body = [[PKMultipartInputStream alloc] init];

NSString *requestString =[self getRequestStringForRange:range andExtension:fileName];
NSData *requestData = [requestString dataUsingEncoding:NSUTF8StringEncoding];

NSString *jsonLengthString = [NSString stringWithFormat:@"%04lu",(unsigned long)requestData.length];
NSData *jsonLengthData = [jsonLengthString dataUsingEncoding:NSUTF8StringEncoding];

[body addPartWithName:@"jsonLength" data:jsonLengthData];
[body addPartWithName:@"json" data:requestData];
[body addPartWithName:@"separator" string:@"\r\n"];
[body addPartWithName:@"fileData" filename:fileName stream:dataStream streamLength:streamSize];

[self.request setHTTPBodyStream:body];
[self.request setTimeoutInterval:60];
NSString *contentType = LI_CONNECTION_CONTENTTYPE;
[self.request addValue:contentType forHTTPHeaderField: @"Content-Type"];

self.connection = [[NSURLConnection alloc] initWithRequest:self.request delegate:self];
_responseData = [NSMutableData data];
[self.connection start];

该文件正在上传3G/4G.当设备连接到某些ADSL ISP的wifi时,代码也可以工作,但在其他一些ISP中代码不起作用,我得到以下错误:

错误域= NSURLErrorDomain代码= -1001"请求超时." 的UserInfo = {NSErrorFailingURLStringKey = http://example.net,_kCFStreamErrorCodeKey = -2102,NSErrorFailingURLKey = HTTP:/example.net:80/AU,NSLocalizedDescription =请求超时,_kCFStreamErrorDomainKey = 4,NSUnderlyingError = 0x16a40410 {错误域= kCFErrorDomainCFNetwork代码= -1001"请求超时." 的UserInfo = {_ kCFStreamErrorCodeKey = -2102,NSErrorFailingURLStringKey = http://example.net,NSErrorFailingURLKey = http://example.net,NSLocalizedDescription =请求超时.,_kCFStreamErrorDomainKey = 4}}}

有没有人知道这是什么问题？

Answer 1

我终于通过添加Content-Length请求解决了我的问题.

当我们不Content-Length向请求添加标头时,NSURLConnection将其作为chunked请求发送,似乎这些问题在分块请求中很常见.

实际上我没有找到这个chunked请求问题的根本原因(我在网上搜索了很多主题,阅读了很多文章,与其他几个程序员交谈,但没有找到任何根本原因,所以我决定使用其他解决方案)但是我为可以在其业务中使用非分块请求的人共享此解决方案.据我所知,大多数分块请求的用法是实时流,我们不知道Content-Length如果你可以添加Content-Length,我建议用它来避免像这样的分块问题.