If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

For those upgrading your WordPress blog to the new 2.0.6 version, take care if you use Feedburner. After upgrading, your Feedburner feed will (at times) give you an invalid xml error. Thankfully, over on NeoSmart they’ve posted an explanation of the error as well as a couple workarounds.

Explanation

FeedBurner uses something called “Conditional Get requests” to ask your server whether or not the page has changed since the last it viewed it, in order to save you some bandwidth. Depending on how popular your site is, FeedBurner may hit up your feed up to hundreds of times a day, so this is a really good idea! Unfortunately, in WordPress 2.0.6, your site doesn’t respond in a way that FeedBurner recognizes. The 304 headers it sends back to let it know that the content hasn’t changed are malformed and corrupt - and FeedBurner has no idea what they mean.