-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Describe the bug
I ran into a problem with my FreshRSS installation. I usually pull the edge docker image version for my deploys. My feed reader (NetNewsWire) couldn't fetch the latest feeds from the instance (not sure if it happened today or it's been like this in the past few days). The web ui worked as expected. I debugged and now things are working fine. What I'm not sure of is if restarting my instance fixed a temporary hang-up of the greader API or if pinning my image version to 1.27.1 fixed the issue. Either way, I am filing a report here in case this is an actual issue in the edge version.
(Issue summarised with Claude Code)
Environment
- FreshRSS Version: 1.27.2-dev (edge image)
- Database: PostgreSQL 17.6
- Client: NetNewsWire (RSS Reader using Google Reader API)
Issue
The POST endpoint /api/greader.php/reader/api/0/stream/items/contents returns empty items array when requesting specific item IDs, while GET requests work correctly.
Request:
curl -X POST "https://example.com/api/greader.php/reader/api/0/stream/items/contents" \
-H "Authorization: GoogleLogin auth=user/token" \
-d "i=1760679231329338&i=1760679231329337&output=json"
Response (incorrect):
{
"id": "user/-/state/com.google/reading-list",
"updated": 1760680510,
"items": []
}Expected behavior
Should return array with requested items (works correctly in 1.27.1 stable)
FreshRSS version
1.27.2-dev
System information
- FreshRSS Version: 1.27.2-dev (edge image)
- Database: PostgreSQL 17.6
- Client: NetNewsWire (RSS Reader using Google Reader API)
Additional context
Impact: RSS readers using POST requests (NetNewsWire, etc.) cannot fetch new articles, though marking as read/unread works.
Workaround: Rollback to FreshRSS 1.27.1 stable