Under the hood
Fixed a bug in the check that decides whether a cached file is still fresh enough to reuse
What
The logic that decides whether a cached copy of a file is recent enough to reuse now correctly reads that file's own last-modified time (rounded down to the millisecond) before calculating its age. Previously it appears to have referenced a variable from the wrong scope.
Why
This fixes the freshness check for cached files, making it correctly reflect the actual file's age rather than possibly using the wrong file's timestamp.