Cached Resource timestamp refresh after loading

[falcon283]

I'm opening this issue based on the topic discussed here

Summary

When, at the app startup, a Disk Cached Resource get loaded from disk via loadIfNeeded() and the resource is still valid a call to receiveDataNotModified() just touch the resource updating the timestamp with the current date. This makes the Resource expiration time much longer then the expected.

Resolution

As you pointed out the issue looks to be here where the call to receiveDataNotModified() touch the resource updating the timestamp.