You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Dutch news site RSS not available in feedparser #1
When I try to add https://telegraaf.nl/rss/ to the feedparser I get an error: "Failed to connect". When I look up the URL in a browser it says: "This XML file does not appear to have any style information associated with it. The document tree is shown below."
Is that the reason why I can't add this to the feedparser?
The browser message about missing style info is normal for RSS feeds and isn’t the cause. The “Failed to connect” error happens because some sites (like telegraaf.nl) block non-browser requests.
In v1.0.1, feedparser now uses browser-like headers and a realistic User-Agent, so this feed should work fine. Make sure you’re on the latest version and try again.
No need for a new ticket just yet; let’s look into these here.
Regarding Telegraaf:
I’m currently unable to reproduce the issue on my end. As you can see in the screenshot below, the feed appears to be loading correctly:
Could you clarify what specific error or behavior you're seeing?
Regarding FD.nl:
I've identified the culprit here. The feed uses a non-standard structure with duplicate tags, which is tripping up the parser. I’m going to implement a fix for this to handle this edge case.
Thanks for your patience and for pointing out these two feeds! I've released v1.0.3 which tackles both issues:
FD.nl: The feed sent over an aggressive structure when parsed, which caused the underlying XML arrays to be ignored. I've mapped the parser to properly natively expose those complex lists and adjusted HTTP headers so it shouldn't get tripped up fetching the RSS.
Telegraaf: I discovered that the thumbnails weren't loading optimally because the feed supplies relative image paths. The integration now automatically resolves those relative links back against the base feed URL to construct proper absolute links for images so they show up beautifully.
Update to the new release and let me know if everything is running smoothly on your end now!
Activity
feat(#1): update HTTP request headers to mimic a browser for improved…
timmaurice commentedon Feb 18, 2026
Hi @DJGizbo,
The browser message about missing style info is normal for RSS feeds and isn’t the cause. The “Failed to connect” error happens because some sites (like telegraaf.nl) block non-browser requests.
In v1.0.1, feedparser now uses browser-like headers and a realistic User-Agent, so this feed should work fine. Make sure you’re on the latest version and try again.
Cheers,
Tim
DJGizbo commentedon Feb 20, 2026
YES! It works now, thank you very much.
DJGizbo commentedon Mar 25, 2026
Hi Tim, same issue again for http://www.telegraaf.nl/rss and https://fd.nl/?rss. Should I open a new ticket?
timmaurice commentedon Mar 26, 2026
Hi DJGizbo,
No need for a new ticket just yet; let’s look into these here.
Regarding Telegraaf:
I’m currently unable to reproduce the issue on my end. As you can see in the screenshot below, the feed appears to be loading correctly:
Could you clarify what specific error or behavior you're seeing?
Regarding FD.nl:
I've identified the culprit here. The feed uses a non-standard structure with duplicate tags, which is tripping up the parser. I’m going to implement a fix for this to handle this edge case.
DJGizbo commentedon Mar 26, 2026
I deleted and re-added Telegraaf and it is working again! Thanks.
Looking forward to the fix, but please take your time ;)
Thanks for your help!
fix(#1): resolve relative image URLs using `urljoin` and update versi…
timmaurice commentedon Mar 27, 2026
Hi @DJGizbo,
Thanks for your patience and for pointing out these two feeds! I've released v1.0.3 which tackles both issues:
Update to the new release and let me know if everything is running smoothly on your end now!
https://github.com/timmaurice/feedparser/releases/tag/1.0.3
DJGizbo commentedon Mar 27, 2026
Thanks again, Tim! It is working perfectly for all my feeds again.
Bought you a coffee to support all your Home Assistant work ;).