This was recently brought to my attention by Adam Messinger who had trouble accessing this blogs’ feeds through a .NET based feed reader. Apparently
…this is caused by a known bug in WP 1.2, which produces HTTP
headers that don’t sit well with .Net since a security patch released early
this fall. Readers written with .Net refuse to process affected WP feeds,
citing an “HTTP protocol violation.”
An easy fix for this can be found at http://technospin.org/index.php?p=14.
Apparently this has been addressed already in the forums and in the CVS from what I see. WordPress 1.2.1 DOES NOT have this fix, but the CVS and all 1.3 Alphas do have it.
So if you are running WordPress 1.2 or WordPress 1.2.1 and have not applied this fix, I suggest that you open up your wp-blog-header.php and replace the “Last Modified” (at line 77) with “Last-Modified”.
Thanks Adam!
Glad to help! š
It seems like this has been addressed in 1.2.1 My wp1.2.1 shows the correct syntax:
// Sending HTTP headers
if (!isset($doing_rss) || !$doing_rss) {
// It is presumptious to think that WP is the only thing that might change on the page.
@header(“Expires: Mon, 26 Jul 1997 05:00:00 GMT”);
// Date in the past
@header(“Last-Modified: ” . gmdate(“D, d M Y H:i:s”) . ” GMT”); // alwa\
…
Newsgator online also trips on this last I hear. They may have changed the code to accept it by now, but it’s always good to fix broken stuff then code around it š