lwindolf / liferea

Liferea (Linux Feed Reader), a news reader for GTK/GNOME
https://lzone.de/liferea
GNU General Public License v2.0
804 stars 131 forks source link

How to clear the cache? #1264

Closed stefanos82 closed 10 months ago

stefanos82 commented 1 year ago

Is there a way to clear the cache for either an individual feed or all feeds at once?

lwindolf commented 11 months ago

I do not get what you mean with cache? Do you want to forget all feed headlines? Or do you want to do something else?

stefanos82 commented 11 months ago

When we right-click on a feed to Update, there are cases where some feed articles are cached and we cannot pull new updates:

< HTTP/1.1 304 Not Modified
< Soup-Debug-Timestamp: 1689535604
< Soup-Debug: SoupMessage 6 (0x5595774d9c60)
< Server: nginx
< Date: Sun, 16 Jul 2023 19:26:44 GMT
< Connection: keep-alive
< ETag: "30af7753a5f7fe9063705497e124e6a2"
< Vary: Accept-Encoding,Cookie
< X-Powered-By: PleskLin

I have had cases where an article had typos and the author of that feed fixed them but due to the aforementioned message, I could see the old article with typos and could not fetch the updated one.

It would be really useful to have something like Firefox's web tools that have a Disable cache button or a clear cache button to force each feed to pull all data anew.

lwindolf commented 11 months ago

Ah you want to disable "Last Modified" and "Etag" timestamp handling. This is actually done upon each startup, so the first fetch of a feed is actually an "uncached" fetch.

stefanos82 commented 11 months ago

Let's say the startup handling is a compulsory behavior; it would be handy to have the manual option too, just in case like in my aforementioned situation.

lwindolf commented 10 months ago

@stefanos82 I understand you use case and it makes sense. At the same time I do only have resource to support one (already complex) use case as is implemented right now.

stefanos82 commented 10 months ago

@stefanos82 I understand you use case and it makes sense. At the same time I do only have resource to support one (already complex) use case as is implemented right now.

No worries :+1: