This is the first post in what I hope is a series, which I’ll call “WordPress Bug Fix Near Saturday”. And while I’m naming things, I’ll call this first post “Episode IV: A New Hope” (to be followed, 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 no longer have to comment out the following line in the file wp-includes/classes.php:
@header("ETag: $wp_etag");
My logs confirm that WordPress is now correctly parsing its own ETags and sending out HTTP 200 and 304 responses as appropriate. The Penultimate Warrior is victorious and undefeated! Note, however, that none of the bugs that I reported before the Warrior started Running Wild® (cp. Going Wild®) have been fixed yet.
Speaking of my web site logs, they contain a list of phrases that were used to find my site from internet search engines. I’d like to share a few of them that have caught my eye:
- instructions+for+using+the+thighmaster
Squeeze, release, repeat. You’re welcome.
- how+do+u+declare+a+pointer+to+an+array+of+pointers+to+int%3f%3f+in+c+language
int * (* ptr)[];
- talk+to+cat+software
That doesn’t exist, Dr. Doolittle. Try meowing.
- cat+lederhosen
I’ve given your IP to the SPCA.
- betamax+the+sausage+and+the+mouse
These aren’t the droids we’re looking for.
- what+does+ns+stand+for+i+cocoa
NeXTSTEP. Next!
- circle+k+employee+uniforms
I’m so very sorry, dude.
- if+jeff+s+usual+is+a+hint+for+a+password+what+is+the+password
Stop trying to hack into my account, you scoundrel!