Keith Devens .com

Hi Keith, which URL do you have set as 301? I've checked our database, and it appears we are getting 200 from http://keithdevens.com/weblog/rss. Sorry for the trouble.

http://keithdevens.com/weblog/?rss was my original feed location. That currently forwards (301) to http://keithdevens.com/weblog?rss, merely as a consequence of my site removing all slashes from the ends of URLs (that's a feature that gets at the URL before my weblog code does), and then on to http://keithdevens.com/weblog/rss, which is my current RSS feed location.

Your software is still fetching the /?rss location, though it seems like it does some caching at some point, because after being redirected to /rss the next time it fetches the feed it checks the correct URL. What's strange is that the subsequent check is consistently only a minute or a few after the first check, and then the next time it checks, hours later, it starts again at the /?rss location. Here're some lines of a grep of my Apache log going back a couple days from the most recent check (note that there are no lines omitted):

65.57.104.88 - - [09/Jan/2005:13:52:51 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [09/Jan/2005:13:52:51 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [09/Jan/2005:13:52:51 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [09/Jan/2005:13:54:09 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [10/Jan/2005:12:26:20 -0500] "GET /weblog/rss HTTP/1.1" 304
65.57.104.88 - - [10/Jan/2005:22:13:16 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [10/Jan/2005:22:13:16 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [10/Jan/2005:22:13:17 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [10/Jan/2005:22:15:24 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:02:47:11 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:02:47:11 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:02:47:11 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:02:48:01 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:04:12:14 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:04:12:14 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:04:12:14 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:04:13:04 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:08:07:44 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:08:07:44 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:08:07:44 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:08:08:59 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:08:57:51 -0500] "GET /weblog/?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:08:57:51 -0500] "GET /weblog?rss HTTP/1.1" 301
65.57.104.88 - - [11/Jan/2005:08:57:51 -0500] "GET /weblog/rss HTTP/1.1" 200
65.57.104.88 - - [11/Jan/2005:09:00:16 -0500] "GET /weblog/rss HTTP/1.1" 200

In addition, there are other periods where it repeatedly requests /rss (the correct location) hours apart, so I'm not sure what it's doing. If you'd like a full grep of this month's log just let me know.

Keith,

Just checking back in, I think I see the problem; we have a duplicate feed for your blog in our db. I had set the 301 feed to not update, but I think a ping set it updating again. I'm going to do a merge, which should eliminate the bad feed. If you continue to notice this, and it's not too much trouble, drop me an email. Sorry for the hassle.

Cool, thanks for fixing it.