[wp-testers] Bug 1275 - RSS Gives 304's

[Michael D Adams]

I added a note to mosquito 
http://mosquito.wordpress.org/view.php?id=1275 but thought I'd ask 
people to look it over here.

Changing the || to an && on line 137 of the latest SVN produces the 
correct 200 v. 304 behavior, as far as I can tell. I'm not sure that 
the logic is perfect, though; I'm unfamiliar with HTTP_IF_NONE_MATCH 
and therefore don't know what the ${X}_etag variables are.

The (edited) line in question is
if ( (strtotime($client_last_modified) <= strtotime($wp_last_modified)) 
&& ($client_etag == $wp_etag) ) {

Hopefully someone can tell me what HTTP_IF_NONE_MATCH is and why what 
I've done is wrong :)
Michael

On Apr 25, 2005, at 8:48 AM, Ryan Boren wrote:

> On Sun, 2005-04-24 at 10:24 -0500, Admiral Justin wrote:
>> All users of builds after 4-17, please check to see if you are having
>> problems with your feeds.  The way to test would be to use an
>> aggregator that respects 304 Not Modified, or to use your browser (I
>> know this works with Firefox loading the raw xml) and load your feed.
>> Then post.  Try reloading the feed.  Several users have already
>> expressed that the feeds report Not Modified when in fact they are.
>> As more research is being done on this, I think having a few more
>> people try it out couldn't hurt.  Especially if it helps
>>  track down the source of this bug.
>
> This is due to changes in wp-blog-header, specifically changesets 2534
> and 2529.
>
> You can try rolling wp-blog-header back to 2529.  If that doesn't help,
> roll back to 2523.
>
> http://trac.wordpress.org/log/trunk/wp-blog-header.php
>
> Ryan