View Single Post
Old 01-10-2024, 08:41 PM   #9182
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,028
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by bigwoof View Post
I wonder if this will also fix the error I have with the browser cache on chrome where if the cache has been around for a while (say a few days), FanFicFare will just throw a "not in cache" error on new books even after you load them up in the cache (which is quite annoying after you spend the time to load up all the new chapters in the cache).
Probably not?

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).

So I don't know what's going on there. Nor do I see any additional info in the cache I could use to better refine it.

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.
JimmXinu is offline   Reply With Quote