Read a WordPress.com site's posts from its API when the feed is behind a browser check (#317)
pelgranepress.com is on WordPress.com, whose CDN answers /feed/, /feed/atom/ and ?feed=rss2 with HTTP 403 and "Checking your browser...", a JavaScript challenge, whatever the User-Agent. The checks that hit it failed for hours (8 in the day before this), and the publisher has not changed anything. The API at public-api.wordpress.com/wp/v2/sites/<host>/posts has the same posts with no check, and each post's guid is the feed's own (https://host/?p=<id>), so the items read from it are the ones already stored. fetch recognises the challenge by its /__challenge/ script, asks the API instead, and parse reads WordPress's posts JSON as a feed. It sends no title or image for the feed, which record_feed keeps as they were. shortcut: the API's default ten posts, as many as WordPress puts in a feed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -10,6 +10,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Fixed
|
||||
|
||||
- A WordPress.com site that answers its feed with a browser check (HTTP 403) is read from WordPress.com's API instead of failing (#317).
|
||||
|
||||
## [1.3.0] - 2026-10-19
|
||||
|
||||
### Added
|
||||
|
||||
Reference in New Issue
Block a user