Bad URL sends 200 (not 404)
-
I have a couple of blogs running on WordPress 2.5.1 installs. When I access a bogus URL at any of my sites, I get a 200 status code back from the server, instead of the desired 404 code. The custom 404 page that I created is displayed, but the response code from the server doesn’t match. Here are a few notes:
- I updated my theme’s 404.php file as specified here in the Codex. This made no change in what was returned.
- I’m not using a static page as my front page (I’m aware of bug 6539).
Am I missing something obvious here? Why should I still be getting a 200 response when I explicitly modify the 404.php header calls?
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
- The topic ‘Bad URL sends 200 (not 404)’ is closed to new replies.