Open ericlathrop opened 1 month ago
The parser would adhere to the HTTP specification and follow the redirect on to the HTML page, which fails to get parsed because it isn't an RSS feed. So it's not a miniflux bug.
I'd try to find some proxy that ignores location redirects, alternatively you could scrape the RSS with curl from a github action, republish it on pages and parse that feed instead. Regardless that's someting for the discussions section rather than an issue.
This website seems to be misconfigured or broken. Try with curl
and you will see:
curl -v https://www.ap.org/feed/
< HTTP/2 301
< date: Sun, 18 Aug 2024 22:28:46 GMT
< content-type: application/rss+xml; charset=UTF-8
< content-length: 190936
< location: https://www.ap.org
< x-powered-by: WP Engine
....
[RSS feed]
This website reply a 301 that redirects to the homepage, but still send the XML feed in the request body.
Miniflux cannot do anything about it.
Its APs nonsense. I jad to use rss.app to make a feed out of their site content. It worked fine.
I'm trying to add https://www.ap.org/feed/ as a feed, but I get this error:
Unable to parse this feed: parser: unable to detect feed format.
If I run
curl https://www.ap.org/feed/
I see a normal RSS feed.They do respond with a 301, even though the RSS is included. The 301 goes to a html page.