[英]How to disable caching in Alamofire
When I send a GET request twice with Alamofire I get the same response but I'm expecting a different one.当我使用 Alamofire 发送两次 GET 请求时,我得到相同的响应,但我期待不同的响应。 I was wondering if it was because of the cache, and if so I'd like to know how to disable it.我想知道是否是因为缓存,如果是,我想知道如何禁用它。
You have a few options.你有几个选择。
let manager: Manager = {
let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
configuration.URLCache = nil
return Manager(configuration: configuration)
}()
let manager: Manager = {
let configuration = NSURLSessionConfiguration.defaultSessionConfiguration()
configuration.requestCachePolicy = .ReloadIgnoringLocalCacheData
return Manager(configuration: configuration)
}()
Both approaches should do the trick for you.这两种方法都应该为您解决问题。 For more information, I'd suggest reading through the documentation for NSURLSessionConfiguration and NSURLCache .有关更多信息,我建议通读NSURLSessionConfiguration和NSURLCache的文档。 Another great reference is NSHipster article on NSURLCache .另一个很好的参考是关于NSURLCache 的NSHipster 文章。
This is what worked for me.这对我有用。
NSURLCache.sharedURLCache().removeAllCachedResponses()
Swift 3斯威夫特 3
URLCache.shared.removeAllCachedResponses()
swift 3, alamofire 4迅速 3,阿拉莫火 4
My solution was:我的解决方案是:
creating extension for Alamofire:为 Alamofire 创建扩展:
extension Alamofire.SessionManager{
@discardableResult
open func requestWithoutCache(
_ url: URLConvertible,
method: HTTPMethod = .get,
parameters: Parameters? = nil,
encoding: ParameterEncoding = URLEncoding.default,
headers: HTTPHeaders? = nil)// also you can add URLRequest.CachePolicy here as parameter
-> DataRequest
{
do {
var urlRequest = try URLRequest(url: url, method: method, headers: headers)
urlRequest.cachePolicy = .reloadIgnoringCacheData // <<== Cache disabled
let encodedURLRequest = try encoding.encode(urlRequest, with: parameters)
return request(encodedURLRequest)
} catch {
// TODO: find a better way to handle error
print(error)
return request(URLRequest(url: URL(string: "http://example.com/wrong_request")!))
}
}
}
and using it:并使用它:
Alamofire.SessionManager.default
.requestWithoutCache("https://google.com/").response { response in
print("Request: \(response.request)")
print("Response: \(response.response)")
print("Error: \(response.error)")
}
func getImage(url: String, completion: @escaping (UIImage?) -> ()) {
let urlRequest = URLRequest(url: URL(string: url)!)
URLCache.shared.removeCachedResponse(for: urlRequest)
//URLCache.shared.removeAllCachedResponses()
Alamofire.request(url).responseData { (dataResponse) in
guard let data = dataResponse.data else {
return completion(nil)
}
completion(UIImage(data: data, scale:1))
}
}
In Alamofire 4 and Swift 3 :在Alamofire 4和Swift 3 中:
// outside function, inside class
var sessionManager: SessionManager!
func someFunc() {
let configuration = URLSessionConfiguration.default
configuration.urlCache = nil
let sessionManager = Alamofire.SessionManager(configuration: configuration)
sessionManager.request("http://example.com/get").responseJSON { response in
// ...
}
}
[This approach doesn't disable caching, it merely makes sure that cached files aren't reused] [这种方法不会禁用缓存,它只是确保不会重用缓存的文件]
An easier way to get past cache problem for a particular call is to just add a random number in the call params.解决特定调用的缓存问题的更简单方法是在调用参数中添加一个随机数。
For Swift 3, you can use, arc4random()
to generate a random number.对于 Swift 3,您可以使用arc4random()
生成随机数。
我通过做来解决它
configuration.urlCache?.removeAllCachedResponses()
Specifically removing a cached response before firing that request again would be more appropriate like:在再次触发该请求之前专门删除缓存的响应会更合适,例如:
let url = "http://google.com"
let urlRequest = URLRequest(url: URL(string: url)!)
URLCache.shared.removeCachedResponse(for: urlRequest)
Alamofire
.request(urlRequest)
.responseJSON(completionHandler: { response in
//handle response
}
You can try to add cache-control to your headers.您可以尝试向标头添加缓存控制。
let headers = ["Authorization": "Bearer \(token)",
"Cache-Control": "no-cache"]
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.