I’m not hosting tiny-rss but I see tiny-rss in my logs.
I have identified two issues with the clients hitting my feed.
When tiny tiny RSS is requesting a feed, it might end up on a feed which change location.
In my case the feed is doing an HTTP 301, aka permanent redirect. Tiny Tiny RSS is following the instructions and goes fetch the feed. So far so good.
18.104.22.168 - - [02/Jan/2019:07:43:58 +0000] "GET /feed.rdf HTTP/1.1" 301 242 "-" "Tiny Tiny RSS/17.4 (http://tt-rss.org/)" 22.214.171.124 - - [02/Jan/2019:07:43:58 +0000] "GET /feed.atom HTTP/1.1" 200 89288 "-" "Tiny Tiny RSS/17.4 (http://tt-rss.org/)"
The issue is that it doesn’t remember it was a permanent redirect.
For example, this IP address does:
grep 126.96.36.199 access.log.1545868800 | grep rdf | grep '01/Jan' | wc -l
48 access in 24h, one every 30 minutes to the
/feed.rdf before following the redirection.
It should probably remember it had received the instructions that the feed had changed location.
Second issue, the caching, the server is setting an ETAG and an expiration date. If the ETAG has not changed, Tiny Tiny RSS should not try reloading the resource.
HTTP/1.1 200 OK Accept-Ranges: bytes Connection: Keep-Alive Content-Length: 89288 Content-Type: application/atom+xml;charset=utf-8 Date: Wed, 02 Jan 2019 07:51:46 GMT ETag: "15cc8-57e5f6761aa40" Expires: Wed, 09 Jan 2019 07:51:46 GMT Keep-Alive: timeout=5, max=100 Last-Modified: Tue, 01 Jan 2019 06:11:45 GMT Server: Apache/2.4.37 (FreeBSD)
from what I gather in my logs it seemts the caching issue has been fixed in the version 18.8+. That’s cool!
17.4 seems to not follow/understand the cache information.
It would be cool to fix the redirect issue too.