Alex Grebenyuk

No, I think you are right. I checked [MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control), and your interpretation seems to be correct. I also haven't worked with HTTP cache in a while, so take this with...

You can switch to a [disk cache](https://kean-docs.github.io/nuke/documentation/nuke/getting-started#Caching) that ignores `cache-control` headers by changing the pipeline configuration: ```swift ImagePipeline.shared = ImagePipeline(configuration: .withDataCache) ```

I'm going to close it because it's been a while. I'm still unsure if there is an issue on the framework side and if there is how to reproduce it....

Thanks you for posting it, @lschaupp. I hope other folks find it useful in the future.

Thanks for the report. I'm going to try to reproduce it using unit tests. If you could provide a sample code to reproduce it, it would also be appreciated.

Hey @hyouuu, can you please check if you are using the same URLs in both of these scenarios?

That's perfect, thanks. That's precisely what the root cause is. **Steps** - Configure the pipeline using `ImagePipeline(configuration: .withDataCache)` (the default [`dataCachePolicy`](https://kean-docs.github.io/nuke/documentation/nuke/imagepipeline/configuration-swift.struct/datacachepolicy) is [`.storeOriginalData`](https://kean-docs.github.io/nuke/documentation/nuke/imagepipeline/datacachepolicy/storeoriginaldata)). - Load an image with URL "https://example.com/image.jpeg"...

So, if you would like to remove the cached image manually, make sure to pass the exact thumbnail options in the request.

The thumbnail issues were fixed in [Nuke 12.6](https://github.com/kean/Nuke/releases/tag/12.6.0). If the issues persistent, please, provide a small sample project or, ideally, a unit test with reproduction steps.

Hey, thanks for the report. From the top of my head, I'm not sure what might might be causing the crash. I see in the report that the Nuke APIs...