From f19800a6279f6923bfcbb099c1e173a1a8463f80 Mon Sep 17 00:00:00 2001 From: Tim Kersey Date: Fri, 12 Jan 2024 13:39:11 -0800 Subject: [PATCH] Should read `stale images` not `state images`. --- Documentation/Nuke.docc/Performance/performance-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Nuke.docc/Performance/performance-guide.md b/Documentation/Nuke.docc/Performance/performance-guide.md index 74b718c46..fc6013f25 100644 --- a/Documentation/Nuke.docc/Performance/performance-guide.md +++ b/Documentation/Nuke.docc/Performance/performance-guide.md @@ -28,7 +28,7 @@ This response is cacheable, and will be *fresh* for 1 hour. When the response be > Tip: Make sure that the images served by the server have [Cache Control](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control) set correctly. -> Important: By default, `URLCache` doesn't serve state images offline. To show a stale image, pass the `URLRequest` with cache policy set to [.returnCacheDataDontLoad](https://developer.apple.com/documentation/foundation/nsurlrequest/cachepolicy/returncachedatadontload) and then perform a second request to refresh the image. +> Important: By default, `URLCache` doesn't serve stale images offline. To show a stale image, pass the `URLRequest` with cache policy set to [.returnCacheDataDontLoad](https://developer.apple.com/documentation/foundation/nsurlrequest/cachepolicy/returncachedatadontload) and then perform a second request to refresh the image. ### L3. Aggressive Disk Cache (Optional)