| layout | title | ref | category | rating | description |
|---|---|---|---|---|---|
post |
NSURLCache |
Foundation |
8.7 |
NSURLCache provides a composite in-memory and on-disk caching mechanism for URL requests to your application. As part of Foundation's URL Loading System, any request loaded through NSURLConnection will be handled by NSURLCache. |
NSURLCache provides a composite in-memory and on-disk caching mechanism for URL requests to your application. As part of Foundation's URL Loading System, any request loaded through NSURLConnection will be handled by NSURLCache.
Network caching reduces the number of requests that need to be made to the server, and improve the experience of using an application offline or under slow network conditions.
When a request has finished loading its response from the server, a cached response will be saved locally. The next time the same request is made, the locally-cached response will be returned immediately, without connecting to the server. NSURLCache returns the cached response automatically and transparently.
As of iOS 5, a shared NSURLCache is set for the application by default. Quoth the docs:
Applications that do not have special caching requirements or constraints should find the default shared cache instance acceptable. An application with more specific needs can create a custom NSURLCache object and set it as the shared cache instance using setSharedURLCache:. The application should do so before any calls to this method.
Those having such special caching requirements can set a shared URL cache in -application:didFinishLaunchingWithOptions: on iOS, or –applicationDidFinishLaunching: on Mac OS X:
- (BOOL)application:(UIApplication *)application
didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
NSURLCache *URLCache = [[NSURLCache alloc] initWithMemoryCapacity:4 * 1024 * 1024
diskCapacity:20 * 1024 * 1024
diskPath:nil];
[NSURLCache setSharedURLCache:URLCache];
}
Caching policies are specified in both the request (by the client) and in the response (by the server). Understanding these policies and how they relate to one another is essential to finding the optimal behavior for your application.
NSURLRequest has a cachePolicy property, which specifies the caching behavior of the request according to the following constants:
NSURLRequestUseProtocolCachePolicy: Caching logic defined in the protocol implementation is used for a particular URL load request. This is the default policy.NSURLRequestReloadIgnoringLocalCacheData: Data should be loaded from the originating source. No existing cache data should be used.NSURLRequestReloadIgnoringLocalAndRemoteCacheData: Not only should the local cache data be ignored, but proxies and other intermediates should be instructed to disregard their caches so far as the protocol allows.NSURLRequestReturnCacheDataElseLoad: Existing cached data should be used, regardless of its age or expiration date. If there is no existing data in the cache corresponding to the request, the data is loaded from the originating source.NSURLRequestReturnCacheDataDontLoad: Existing cache data should be used, regardless of its age or expiration date. If there is no existing data in the cache corresponding to the request, no attempt is made to load the data from the originating source, and the load is considered to have failed, (i.e. "offline" mode).NSURLRequestReloadRevalidatingCacheData: Existing cache data may be used provided the origin source confirms its validity, otherwise the URL is loaded from the origin source.
It may not surprise you that these values are poorly understood and often confused with one another.
Adding to the confusion is the fact that NSURLRequestReloadIgnoringLocalAndRemoteCacheData and NSURLRequestReloadRevalidatingCacheData aren't even implemented! (Link to Radar).
So here's what you actually need to know about NSURLRequestCachePolicy:
| Constant | Meaning |
|---|---|
| UseProtocolCachePolicy | Default behavior |
| ReloadIgnoringLocalCacheData | Don't use the cache |
| ReturnCacheDataElseLoad | Use the cache (no matter how out of date), or if no cached response exists, load from the network |
| ReturnCacheDataDontLoad | Offline mode: use the cache (no matter how out of date), but don't load from the network |
Because NSURLConnection is designed to support multiple protocols—including both FTP and HTTP/HTTPS—the URL Loading System APIs specify caching in a protocol-agnostic fashion. For the purposes of this article, caching will be explained in terms of HTTP semantics.
HTTP requests and responses use headers to communicate metadata such as character encoding, MIME type, and caching directives.
By default, NSURLRequest will use the current time to determine whether a cached response should be returned. For more precise cache control, the following headers can be specified:
If-Modified-Since- This request header corresponds to theLast-Modifiedresponse header. Set the value of this to theLast-Modifiedvalue received from the last request to the same endpoint.If-None-Match- This request header corresponds to theEtagresponse header. Use theEtagvalue received previously for the last request to that endpoint.
An NSHTTPURLResponse contains a set of HTTP headers, which can include the following directives for how that response should be cached:
Cache-Control- This header must be present in the response from the server to enable HTTP caching by a client. The value of this header may include information like itsmax-age(how long to cache a response), and whether the response may be cached withpublicorprivateaccess, orno-cache(not at all). See theCache-Controlsection of RFC 2616 for full details.
In addition to Cache-Control, a server may send additional headers that can be used to conditionally request information as needed (as mentioned in the previous section):
Last-Modified- The value of this header corresponds to the date and time when the requested resource was last changed. For example, if a client requests a timeline of recent photos,/photos/timeline, theLast-Modifiedvalue could be set to when the most recent photo was taken.Etag- An abbreviation for "entity tag", this is an identifier that represents the contents requested resource. In practice, anEtagheader value could be something like theMD5digest of the resource properties. This is particularly useful for dynamically generated resources that may not have an obviousLast-Modifiedvalue.
Once the server response has been received, the NSURLConnection delegate has an opportunity to specify the cached response in -connection:willCacheResponse:.
NSCachedURLResponse is a class that contains both an NSURLResponse with the cached NSData associated with the response.
In -connection:willCacheResponse:, the cachedResponse object has been automatically created from the result of the URL connection. Because there is no mutable counterpart to NSCachedURLResponse, in order to change anything about cachedResponse, a new object must be constructed, passing any modified values into –initWithResponse:data:userInfo:storagePolicy:, for instance:
- (NSCachedURLResponse *)connection:(NSURLConnection *)connection
willCacheResponse:(NSCachedURLResponse *)cachedResponse
{
NSMutableDictionary *mutableUserInfo = [[cachedResponse userInfo] mutableCopy];
NSMutableData *mutableData = [[cachedResponse data] mutableCopy];
NSURLCacheStoragePolicy storagePolicy = NSURLCacheStorageAllowedInMemoryOnly;
// ...
return [[NSCachedURLResponse alloc] initWithResponse:[cachedResponse response]
data:mutableData
userInfo:mutableUserInfo
storagePolicy:storagePolicy];
}
If -connection:willCacheResponse: returns nil, the response will not be cached.
- (NSCachedURLResponse *)connection:(NSURLConnection *)connection
willCacheResponse:(NSCachedURLResponse *)cachedResponse
{
return nil;
}
When left unimplemented, NSURLConnection will simply use the cached response that would otherwise be passed into -connection:willCacheResponse:, so unless you need to change or prevent caching, this method does not need to be implemented in the delegate.
Just like its unrelated-but-similarly-named cohort, NSCache, NSURLCache is not without some peculiarities.
As of iOS 5, disk caching is supported, but only for HTTP, not HTTPS, requests (though iOS 6 added support for this). Peter Steinberger wrote an excellent article on this subject, after digging into the internals while implementing his own NSURLCache subclass.
Another article by Daniel Pasco at Black Pixel describes some unexpected default behavior when communicating with servers that don't set cache headers.
NSURLCache reminds us of how important it is to be familiar with the systems we interact with. Chief among them when developing for iOS or Mac OS X is, of course, the URL Loading System.
Untold numbers of developers have hacked together an awkward, fragile system for network caching functionality, all because they weren't aware that NSURLCache could be setup in two lines and do it 100× better. Even more developers have never known the benefits of network caching, and never attempted a solution, causing their apps to make untold numbers of unnecessary requests to the server.
So be the change you want to see in the world, and be sure to always start you app on the right foot, by setting a shared NSURLCache in -application:didFinishLaunchingWithOptions:.