Quote:
Originally Posted by JimmXinu
Looking at the FFF debug output, Chrome doesn't update the 'creation' timestamp in the cache when clicking back and forth between chapters, on plain reload (ctrl-r), but it does on forced reload (ctrl-shft-r).
When clicking back and forth between chapters, Chrome's F12 networking debug shows a 200 OK (successful download) instead of a 304 Not Modified, which I see for plain reload (ctrl-r).  |
Thanks for the explanation! :-)
Quote:
Originally Posted by JimmXinu
What I can offer for that issue is: you can change FFF's browser_cache_age_limit setting. It's a float value of hours, -1 will use any found cache entry, regardless of age.
|
yeah, I'm already using that and it helps somewhat. some of the quirks I see are
1. the cache just stops working after a few days and FFF outputs a "file not in cache" error (forgot the actual error name) -- solution: clear the cache frequently before accessing the new pages you want FFF to download
2. some epubs (especially new single chapter epubs) *always* get reloaded by FFF even if you have a fresh cache and have access that epub and force-reload etc. -- solution: live with it. it just makes the whole download process a little longer and causes chrome windows to appear in the middle of your work :-)