Refreshing every feed still asks each one only for changes #77

Closed
opened 2026-09-28 16:45:08 -07:00 by rays · 1 comment
Owner

Check every feed (and a single feed's refresh) sends force, but force only skips the not-due wait: the request still carries the stored ETag and Last-Modified, so a feed that has not changed answers 304 and is not read. A refresh someone asks for should read the feeds in full, as the scan at 23:22:27 on 2026-09-28 showed when anil-dash came back not modified and so got no site icon. Reported by the user.

Check every feed (and a single feed's refresh) sends force, but force only skips the not-due wait: the request still carries the stored ETag and Last-Modified, so a feed that has not changed answers 304 and is not read. A refresh someone asks for should read the feeds in full, as the scan at 23:22:27 on 2026-09-28 showed when anil-dash came back not modified and so got no site icon. Reported by the user.
rays added the bug label 2026-09-28 16:45:08 -07:00
Author
Owner

Fixed in bae22e5: a forced scan (check every feed, a feed's refresh, pull to refresh, ipx fetch --force) drops the stored ETag and Last-Modified and reads each feed in full; scheduled scans keep them. Deployed; a forced scan of anil-dash now reads the feed instead of stopping at not modified.

Fixed in bae22e5: a forced scan (check every feed, a feed's refresh, pull to refresh, ipx fetch --force) drops the stored ETag and Last-Modified and reads each feed in full; scheduled scans keep them. Deployed; a forced scan of anil-dash now reads the feed instead of stopping at not modified.
rays closed this issue 2026-09-28 16:47:58 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#77