According to my server logs, I'm frequently getting people browsing my site to access
/tag/undefined, like this:
***.***.***.*** - - [03/Oct/2012:15:19:26 +0000] "GET /archives/undefined HTTP/1.0" 404 19154 "http://server/archives/1333" "Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; BTRS125042; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)"
What happened? I assume they got returned the default "Not found" page?
Now, my site is set up to list the blog posts when the user goes to
http://server/blog, while my front page is static. The format I'm using for blog post URLs is
http://server/archives/1234, tags and categories work likewise, e.g.
I assume the issue I described above is what happens when people simply delete the post number or tag/category name at the end – I have so far not been able to consciously reproduce this myself. When I try to do what I think happens, I get this:
***.***.***.*** - - [03/Oct/2012:15:51:41 +0000] "GET /archives HTTP/1.0" 404 11546 "-" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.79 Safari/537.4"
Now, is there anything I can do to serve e.g. a sitemap (already exists as a page), or the default blog post listing instead of getting people to end up at
/archives/undefined? In case it's important, I'm using Twentyten as a theme.