Comments on: WordPress Bug Friday: Wasting your bandwidth

By: Lap Cat Software Blog » Blog Archive » WordPress Bug Fix!

Lap Cat Software Blog » Blog Archive » WordPress Bug Fix! — Sat, 12 Apr 2008 14:29:06 +0000

[...] no doubt, by “Episode V: All Hope Dashed”). I’m very happy to report that the ETag parsing bug has been fixed in WordPress 2.0.7. Thus, if you’re running WordPress 2.0.7 on your site, you [...]

By: Anonymous

Anonymous — Wed, 27 Dec 2006 01:51:06 +0000

Unfortunately, syndicators like Bloglines require both the Etag and Last-modified headers in order for it to them to respect a 304.

By: Peter Hosey

Peter Hosey — Sun, 17 Dec 2006 19:14:10 +0000

Thanks to both of you! I’ve just applied this to my own blog. I’ll see how well it works.

As I mentioned on my own blog (spam prevention has been a topic there lately), I don’t use Akismet â€” when the Adium Trac was using it, we had a *lot* of users blocked from creating or commenting on tickets by the Trac Akismet plug-in. That, combined with their lack of detailed explanation of the operation of the plug-in, makes it one of my last resorts (along with Bad Behavior).

By: Jeff

Jeff — Sun, 17 Dec 2006 17:53:40 +0000

His comment got marked as spam by Akismet, so I didn’t see it until after I approved yours. That is pretty funny.

By: Daniel Jalkut

Daniel Jalkut — Sun, 17 Dec 2006 17:29:43 +0000

Heh, the comment from charles wasn’t there when I submitted. Honest!

By: Daniel Jalkut

Daniel Jalkut — Sun, 17 Dec 2006 16:26:17 +0000

I also ran into the 304 dysfunction, and fixed it in conjunction with adding support for WP-Cache, so I could reduce my processor usage at the same time:

http://www.red-sweater.com/blog/128/smokin-fast-blog

By: charles

charles — Sun, 17 Dec 2006 16:01:15 +0000

http://www.red-sweater.com/blog/128/smokin-fast-blog