Asks the delegate whether the data (or upload) task should store the response in the cache.
- iOS 7.0+
- macOS 10.9+
- tvOS 9.0+
- watchOS 2.0+
The session containing the data (or upload) task.
The data (or upload) task.
The default caching behavior. This behavior is determined based on the current caching policy and the values of certain received headers, such as the
A block that your handler must call, providing either the original proposed response, a modified version of that response, or
NULLto prevent caching the response. If your delegate implements this method, it must call this completion handler; otherwise, your app leaks memory.
The session calls this delegate method after the task finishes receiving all of the expected data. If you don’t implement this method, the default behavior is to use the caching policy specified in the session’s configuration object. The primary purpose of this method is to prevent caching of specific URLs or to modify the
user dictionary associated with the URL response.
This method is called only if the
NSURLProtocol handling the request decides to cache the response. As a rule, responses are cached only when all of the following are true:
The request is for an HTTP or HTTPS URL (or your own custom networking protocol that supports caching).
The request was successful (with a status code in the
The provided response came from the server, rather than out of the cache.
The session configuration’s cache policy allows caching.
URLRequestobject's cache policy (if applicable) allows caching.
The cache-related headers in the server’s response (if present) allow caching.
The response size is small enough to reasonably fit within the cache. (For example, if you provide a disk cache, the response must be no larger than about 5% of the disk cache size.)