Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect when remote file has changed. #136

Open
ikreymer opened this issue Nov 15, 2022 · 1 comment
Open

Detect when remote file has changed. #136

ikreymer opened this issue Nov 15, 2022 · 1 comment

Comments

@ikreymer
Copy link
Member

For a remote WARC or WACZ, need to detect if it has changed and due a purge cache + full reload before trying to load anything, as all previously cached data should be considered invalid.

This is a bit tricky as need to determine when to check the file after initial load, and how to determine that it's changed.
(Look for etag? Just file size perhaps for now?)
The cached data may still be usable, as long as no additional data is loaded, so maybe a warning is needed instead of triggering an automatic reload..

@llamerr
Copy link

llamerr commented Jan 22, 2023

I'm not sure If I have same issue...

  1. I create file1.wacz (snapshot of page1), open it and see content at time1
  2. I create updated file from the same site (snapshot of page1, but newer), and name it with the same name file1.wacz, and place it at the same place. When I open it, I see old cached version at time1. When I rename it to file2.wacz, it shows correct content at time2. I rename it back to file1.wacz, open it again, and again see old content at time1. I tried to do Force Reload, but it's just stuck at 0% and never progresses. Datetime of that file1.wacz is updated to newer time (and newer size) when it changed

I ended up deleting c:\Users%USER%\AppData\Roaming\replaywebpage\ completely and that finally cleared the cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants