我有一个应用程序，可以在Xcode6-Beta1和Xcode6-Beta2与iOS7和iOS8上正常工作。但是对于Xcode6-Beta3, Beta4, Beta5，我在iOS8上面临网络问题，但在iOS7上一切都很好。我得到错误“网络连接丢失”。错误如下:
Error: ErrorDomain =NSURLErrorDomain Code=-1005 "The network connection was lost."UserInfo=0x7ba8e5b0 {NSErrorFailingURLStringKey=， _kCFStreamErrorCodeKey=57, NSErrorFailingURLKey=， NSLocalizedDescription=网络连接丢失。， _kCFStreamErrorDomainKey=1, NSUnderlyingError=0x7a6957e0 "The network connection was lost."｝
我使用AFNetworking 2。X和下面的代码片段进行网络调用:
AFHTTPRequestOperationManager *manager = [AFHTTPRequestOperationManager manager];
[manager setSecurityPolicy:policy];
manager.requestSerializer = [AFHTTPRequestSerializer serializer];
manager.responseSerializer = [AFHTTPResponseSerializer serializer];
[manager POST:<example-url>
parameters:<parameteres>
success:^(AFHTTPRequestOperation *operation, id responseObject) {
NSLog(@“Success: %@", responseObject);
} failure:^(AFHTTPRequestOperation *operation, NSError *error) {
NSLog(@"Error: %@", error);
}];
我尝试了NSURLSession，但仍然收到相同的错误。
我在iOS 8设备上运行时也遇到了这个问题。
这里有更详细的说明，似乎是iOS试图使用已经超时的连接。
我的问题与那个链接中解释的Keep-Alive问题不一样，但它似乎是相同的最终结果。
我已经通过运行一个递归块纠正了我的问题，每当我收到一个错误-1005，这使得连接最终通过，即使有时递归可以在连接工作之前循环100+次，然而，它只增加了一秒钟的运行时间，我打赌这只是需要调试器为我打印NSLog的时间。
下面是我如何用AFNetworking运行递归块:
将此代码添加到连接类文件中
// From Mike Ash's recursive block fixed-point-combinator strategy https://gist.github.com/1254684
dispatch_block_t recursiveBlockVehicle(void (^block)(dispatch_block_t recurse))
{
// assuming ARC, so no explicit copy
return ^{ block(recursiveBlockVehicle(block)); };
}
typedef void (^OneParameterBlock)(id parameter);
OneParameterBlock recursiveOneParameterBlockVehicle(void (^block)(OneParameterBlock recurse, id parameter))
{
return ^(id parameter){ block(recursiveOneParameterBlockVehicle(block), parameter); };
}
然后这样使用它:
+ (void)runOperationWithURLPath:(NSString *)urlPath
andStringDataToSend:(NSString *)stringData
withTimeOut:(NSString *)timeOut
completionBlockWithSuccess:(void (^)(AFHTTPRequestOperation *operation, id responseObject))success
failure:(void (^)(AFHTTPRequestOperation *operation, NSError *error))failure
{
OneParameterBlock run = recursiveOneParameterBlockVehicle(^(OneParameterBlock recurse, id parameter) {
// Put the request operation here that you want to keep trying
NSNumber *offset = parameter;
NSLog(@"--------------- Attempt number: %@ ---------------", offset);
MyAFHTTPRequestOperation *operation =
[[MyAFHTTPRequestOperation alloc] initWithURLPath:urlPath
andStringDataToSend:stringData
withTimeOut:timeOut];
[operation setCompletionBlockWithSuccess:
^(AFHTTPRequestOperation *operation, id responseObject) {
success(operation, responseObject);
}
failure:^(AFHTTPRequestOperation *operation2, NSError *error) {
if (error.code == -1005) {
if (offset.intValue >= numberOfRetryAttempts) {
// Tried too many times, so fail
NSLog(@"Error during connection: %@",error.description);
failure(operation2, error);
} else {
// Failed because of an iOS bug using timed out connections, so try again
recurse(@(offset.intValue+1));
}
} else {
NSLog(@"Error during connection: %@",error.description);
failure(operation2, error);
}
}];
[[NSOperationQueue mainQueue] addOperation:operation];
});
run(@0);
}
您将看到我使用了一个AFHTTPRequestOperation子类，但添加了您自己的请求代码。重要的部分是调用递归(@offset.intValue+1));使该块再次被调用。
我们有这个确切的错误，它原来是NSURLRequest的底层HTTP实现的问题:
据我们所知，当iOS 8/9/10/11接收到一个带有keep - alive头的HTTP响应时，它会保留这个连接以供以后重用(这是应该的)，但它会保留它的时间超过keep - alive头的超时参数(它似乎总是保持连接活跃30秒)。
然后，当应用程序在不到30秒后发送第二个请求时，它会尝试重新使用可能已经被服务器丢弃的连接(如果超过了真正的Keep-Alive时间)。
以下是我们目前找到的解决方案:
Increase the timeout parameter of the server above 30 seconds. It looks like iOS is always behaving as if the server will keep the connection open for 30 seconds regardless of the value provided in the Keep-Alive header. (This can be done for Apache by setting the KeepAliveTimeout option.
You can simply disable the keep alive mechanism for iOS clients based on the User-Agent of your app (e.g. for Apache: BrowserMatch "iOS 8\." nokeepalive in the mod file setenvif.conf)
If you don't have access to the server, you can try sending your requests with a Connection: close header: this will tell the server to drop the connection immediately and to respond without any keep alive headers. BUT at the moment, NSURLSession seems to override the Connection header when the requests are sent (we didn't test this solution extensively as we can tweak the Apache configuration)
当传递一个NSURLRequest到一个NSURLSession而没有设置请求的HTTPMethod时，我击中了这个错误。
NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:urlComponents.URL];
ErrorDomain =NSURLErrorDomain Code=-1005 "The network connection was lost."
不过，添加HTTPMethod，连接就可以正常工作了
NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:urlComponents.URL];
[request setHTTPMethod:@"PUT"];
