Critical Error Message when Validating

[IncompleteSportsman]

I am getting this error when trying to get my feed listed:

CRITICAL Channel doesn't contain any enclosures (code: 2000)

My feed is http://www.blogtalkradio.com/feeds/sportsman could someone please check it out and tell me what I'm doing wrong? Thanks =)

[Yotto]

Two quick things I notice. One, you have stylesheet information. I found this out because I had to download the rss file becasue your host tried to be helpful when I accessed it with my browser (That second part isn't your fault but it always bugs me). I removed the second set of brackets:

<?xml-stylesheet type='text/xsl' href='/feeds/rss.xsl'?>

And then my browser would parse it. That is possibly all that's wrong.

The second thing I noticed is that it's all on one line. I don't know if that hurts validation, but it's bad form and some podcatchers could choke if your rss feed is only one line. Generally, you should have every single tag on its own line. Check my feed, http://planetretcon.com/podcast/feed.xml for an example.

[BrynM]

Hi IncompleteSportsman. Yotto is on the right track for your warnings. The "Unknown XML version" warning is being caused by all of your feed being on a single line. From what I understand, there's been some debate regarding newlines in the spec that I won't get into. Suffice to say that we'll try to handle them as gracefuly as possible, but you would still be okay submitting your feed with warnings.

The real issue is your critical error. Your enclosure is getting redirected from "http://blogtalkradio.com/feeds/podcasts/6963.mp3" to "http://boss.streamos.com/download/blogtalkradio/show_6963.mp3".

The problem is that your provider is returning "HTTP/1.1 404 Not Found" when our validator requests the enclosure. When I look at it from a web broswer, the server returns "HTTP/1.x 302 Found", which is the proper response for a redirect. I'm not sure how or why your provider's server is responding in this manner, but unfortunately I have no control over it. If you can look at your logs or statistics for our validator's user agent it might give me more information to help solve this issue. The user agent we send is "PCA/0.41 (Podcast Alley; Feed Submission Validator; +http://www.podcastalley.com/)".