mirror of
https://github.com/volatilityfoundation/volatility3.git
synced 2026-08-22 14:32:21 +02:00
This effectively means that the FileTranslationLayer will reuse the cached file even with multiple opens, but rerunning python, or starting a new context (with a new FileTranslationLayer but on the same URL) will cause a redownload whether necessary or not. This ensures that running volatility as an engine (inside a long lived python session) will not prevent a file being checked again later. Other caching mechanisms (such as last-modified) should be used to determine if the cached file is still valid. Note this may cause issues if plugins run concurrently.