WordPress 2.5 test post
This is just the typical test post. I wasn’t going to upgrade yet, but there is apparently an exploit for WordPress 2.3.3 (or perhaps some earlier version, my source is a little sketchy with the details).
I though I caught the bug, and searched around for more info. This page talks about “hidden link injection,” while this page has a different exploit regarding a new directory. I seem to have neither of these.
What’s really weird about WordPress now (and before the upgrade), is that it seems that my blog is sending - in response to a request for my RSS feed - zip compressed content whether or not it’s requested or even supported by the reader doing the request. I have no idea why this started happening all of a sudden.
At least, thanks to cURL, I know what the heck is going on.
$ curl http://standardmischief.com/blog/feed/|head
About 50% of the time this will feed me garbage. The head command it there to limit the scope of the garbage.
$ curl --compressed http://standardmischief.com/blog/feed/|head
Nearly the same command, but the –compressed option actually requests compression and decodes it if it arrives that way.
Stumped.
Update, 10 minutes later: As I was composing the service request, the issue seemed to have disappeared. I’ll hold off and keep an eye on the problem. My feed has been off all day (I suppose my reader does not accept gzip), but it’s working fine now.
Update 2: Here’s a terminal screenshot: (179k)
Philip Welch Says :
Feed receives fine in Safari at the moment.
2008-04-13 03:40 PermalinkStandard Mischief Says :
Thanks for the feedback. Now that I’ve figured out the garbage was gzip, I’d be willing to bet that Safari can handle gzip content (unzipping it on the fly). Iceweasel can too, but I suppose that Akregator, my feed reader, can’t.
That would explain why I could see my blog all day, but my feed appeared broken.
2008-04-13 10:51 Permalink