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
wrongly returns empty enclosure urls for http://www.tatw.co.uk/podcast.xml #7
The enclosures in the have non-null urls when you look at it. The W3C feed validator says it fails to validate due to a number of silly issues, but does not come up with any problems with its enclosures.
but this feed doesn't have any. Hence it fails to parse by the RSS2 parser/importer.
This library tries to make a best effort in case of feed parse errors, but the code paths that work with this untyped representation is less exercised. And it is preferable if we can avoid an untyped/unparseable representation to start with.
Push a pair of fixes; allowing such description-less RSS2 feeds to parse + fixed a bug in the untyped case for getItemEnclosure.
Activity
sof commentedon Sep 28, 2013
The feed validator does try to tell you that the feed is invalid -- RSS2 s must have a description,
http://cyber.law.harvard.edu/rss/rss.html#requiredChannelElements
but this feed doesn't have any. Hence it fails to parse by the RSS2 parser/importer.
This library tries to make a best effort in case of feed parse errors, but the code paths that work with this untyped representation is less exercised. And it is preferable if we can avoid an untyped/unparseable representation to start with.
Push a pair of fixes; allowing such description-less RSS2 feeds to parse + fixed a bug in the untyped case for getItemEnclosure.
joeyh commentedon Feb 10, 2015
Does "push a pair of fixes" mean this got fixed? Bug is still listed as open.