Processing of incorrect RSS
I have subscribed to certain RSS Ont of them (Debian - https://www.debian.org/News/news) recently I noticed it returns invalid XML and TB doesn't get any results from it.
This error will appear until this news is out of date.
Can this error be processed correctly? This feed is not the only returned such response. Time to time I faced this error from several feeds.
I understand it is not the TB bug, but it would be easier to processed it here instead of reporting to every feed provider.
Or are there another solutions?
All Replies (4)
I added the feed to TB 91.0.3/W10, as you can see in the attached picture. It also works in TB 78. Maybe it's a bug with the Linux version.
When the feed processor makes a request to the feed url, it does so requesting a mime type of 'text/xml', since that is the ancient specification requirement for atom/rss feeds - that it be valid xml. If the document is invalid xml, the core gecko parser will throw an error (which you see in console) and the document never gets to the higher level feed code in Thunderbird.
Could this be changed? The mime type could be 'text' and then anything goes and the feed processor could do parsing on each <item> and other error checking instead of leveraging core. Don't expect this to happen.
Your recourse is to tell the publisher to follow the specs. And read the "How to..." guide linked on this page.
sfhowes сказал(а)
I added the feed to TB 91.0.3/W10, as you can see in the attached picture. It also works in TB 78. Maybe it's a bug with the Linux version.
It would be strange if this issue only for Linux version. Does the Gecko work different way on different platforms? If yes, why? As you can see I've attached a screenshot from the firefox browser.
Since 2021-10-09 I began getting news again. It seems issued news has left the RSS.
alta88 сказал(а)
When the feed processor makes a request to the feed url, it does so requesting a mime type of 'text/xml', since that is the ancient specification requirement for atom/rss feeds - that it be valid xml. If the document is invalid xml, the core gecko parser will throw an error (which you see in console) and the document never gets to the higher level feed code in Thunderbird. Could this be changed? The mime type could be 'text' and then anything goes and the feed processor could do parsing on each <item> and other error checking instead of leveraging core. Don't expect this to happen. Your recourse is to tell the publisher to follow the specs. And read the "How to..." guide linked on this page.
This feed worked well before and only that news has broken parsing process. Btw, feed works well now (without specified news).