GNOME Bugzilla – Bug 329813
Podcast : some feeds don't work
Last modified: 2006-03-12 10:46:32 UTC
This bug has been opened on https://launchpad.net/distros/ubuntu/+source/rhythmbox/+bug/30355 "I have subscribed to 3 podcasts from this radio station : http://www.europe1.fr/podcast/podcast.jsp RB used to work fine with them, but recently it started refusing to update the feeds, complaining that : "There was a problem adding this podcast. Please verify the URL: http://www.europe1.fr/podcast/connaissance.jsp" I tried with another podcast program ("Penguin TV"), just to make sure the feeds are still okay, and they are. So must be RB..." Could be a gstreamer0.10 bug, feel free to reassign
That url returns the wrong mime-type (text/html), and PenguinTV is just more lax about what it accepts. Rhythmbox will accept things with the wrong mime-type if they end in ".rss" or ".xml". I've seen a number of people accidently copy the wrong URL, and try to use the URL of the description page instead of the feed, and this is the best protection against that. Usually Rhythmbox can tell anyway, although there are pages which look enough like an RSS feed to confuse programs. There are two options: 1) We leave it as is, and mark WONTFIX. Then we complain to the authors that their feed is broken, as it is technically not an RSS feed. 2) We change it to remove the check, which makes the feed work. However this can cause Rhythmbox to get confused if people accidently give the URL of some non-RSS thing.
1) isn't a good solution. People will stop using RB's podcast support if other tools work with podcasts that have the wrong mime-typoe. 2) why not attempt to parse what you download? If it successfully parses as a podcast feed, then use it. If it doesn't parse, raise an error.
That was probably a gst0.10 bug since it works fine now, feel free to close the bug
It actually work now because the feed generation script has been fixed, and uses the mime-type text/xml. It doesn't answer the issue of how far we should go to support non-standard (i.e. broken) feeds.
I think we should not force that against users. Maybe opening a warning dialog in the case the mime-type is uncorrect?
Created attachment 60235 [details] [review] ask for invalid feeds. This makes RB ask when encountering a feed of the wrong mime-type. The wording could be better.
Created attachment 60392 [details] [review] better patch This version doesn't complain about the invalid feed after you tell it that you don't want to load it.
Patch committed to cvs.