描述
Is your feature request related to a problem? Please describe.
FreshRSS is currently very vague when it encounters issues with feeds. When creating scraped feeds with XPath, this can make debugging very difficult.
This vagueness issue applies to regular RSS feeds as well. Some of my YouTube feeds will randomly fail to fetch, but seem completely fine when I manually refresh them. As the administrator, I can't determine if this is the result of a request timeout, a network issue, or the server refusing my request.
Use case
I want to pull data from https://www.n2yo.com/satellites/?c=30&p=A, which provides a list of satellites in chronological order. My XPaths work correctly when executed in the browser, xmltest complains about bad entities, but FreshRSS just fails to pull in the feed, throwing an unhelpful HTML+XPath Web scraping failed for [https://www.n2yo.com/satellites/?c=30&p=A] into the log.
Even as the FreshRSS administrator, I can't see more detailed information about why FreshRSS has failed.
Describe the solution you’d like
FreshRSS should provide more precise information on where it failed. Such as if it failed to parse the document, or which XPath stage it errored out on.
At minimum, FreshRSS should make available the status code that it gets served, in addition to the headers the server returned.
Being able to pull the document as how FreshRSS itself sees it would also be very helpful, as FreshRSS may be served a differently formatted page than an actual browser, or may not be served the expected page at all (such as a captcha).
Describe alternatives you’ve considered
No response
Additional context
No response