Support » Fixing WordPress » When is a 404 not a 404?

  • I can honestly say that I’ve never seen anything quite like this…

    I upgraded from 1.5 to 2.0 once it went stable, and all was well. I regenerated my permalinks as well, and the bare-bones .htaccess file was created just fine. Links to articles work great, categories, etc….

    I loaded my RSS feeds in my browser from their legacy locations of, /wp/wp-rss2.php, /wp/feed.php and /wp/wp-atom.php — this brought up the correct output in the browser.

    I noticed that my bloglines and livejournal rss ( weren’t updating.

    I headed for the access log on my server and see this: - - [09/Jan/2006:15:41:15 -0500] "GET /wp/wp-rss2.php HTTP/1.1" 404 28981 "-" "FeedFetcher-Google; (+" "-" - - [09/Jan/2006:15:33:02 -0500] "GET /wp/wp-commentsrss2.php HTTP/1.1" 404 10145 "-" "PluckFeedCrawler/2.0 (compatible; Mozilla 4.0; MSIE 5.5;; 0 subscribers)" "-" - - [09/Jan/2006:15:29:33 -0500] "GET /wp/wp-rss2.php HTTP/1.0" 404 27877 "-" "Drupal (+" "-"

    When I pull it up in the browser manually, AND IT DISPLAYS, (cleared cache, tried fresh machines) I get this in the log; - - [09/Jan/2006:15:37:59 -0500] "GET /wp/wp-rss2.php HTTP/1.1" 404 29562 "-" "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5" "-"

    Feed validator hates this too:

    It appears that Technorati has decided to use the path on its own, but nobody else seems to like that idea.

  • The topic ‘When is a 404 not a 404?’ is closed to new replies.