Bad links to RSS feeds

I had the same problem, so I just edited my template to point to the correct URL’s.

Do you have permalinks enabled? (under options/permalinks in your admin page)

Yes. That wasn’t the problem, but I did figure it out. For one reason or another, the information that the Permalink page now tells me to put in the .htaccess file is not the same information that it originally told me to use when I chose the same permalink structure on version 1.0.2 (I use 1.2RC now). So I copied the suggested code and pasted it over the previously-suggested code in .htaccess, and it seems to be working now.
John262: You should probably do that, too. Hard-linking the files in the meta area will solve the specific problem I identified before, but leaves a separate problem unsolved: you’ll still get the pointer to https://www.yourdomain.com/feed/rss2/ in the headers, which aggregators like Bloglines rely on to find your RSS feeds. By changing back the original code and making the appropriate fixes to .htaccess, https://www.yourdomain.com/feed/rss2/ will work, as it should.

Thanks. I hadn’t thought of that.

I have also encountered a similar with the links to my RSS feed. My server does not support ModRewrite in the .htaccess file, so I tried the new feature of creating a Permalink using the index.php file. My Permalink looks like this:
/index.php/archives/%year%/%monthnum%/%day%/%postname%/
I have tested my site and all of my post, category and archive links work correctly (thanks to the developer for this great feature). However, my rss link is as follows
https://myhost.com/feed/rss2/
Since I do not have a ModRewrite rule, this is not a valid link. If I remove the Permalinks rule, then the link goes back to a valid link:
https://myhost.com/wp-rss2.php
For the moment, I will have to hard-code this path in my template to be able to use the new Permalinks and still have a valid RSS link. It would be good in the next update release to leave the RSS link to point directly to the php file if you use index.php in your Permalink or find some other way to correct this.

Woohoo, I had the same problem. Now I don’t! Thanks!