Digg’s Sad HTTP Error handling.
Digg has lame HTTP error handling.
Fetch any Digg page which should 404:
Let’s try to fetch http://digg.com/asdfffffffffsdf (which surely won’t exist).
HTTP/1.1 302 Found
FOUND? Are you sure?
Let’s check out http://digg.com/error
HTTP/1.1 404 Not Found
What? Wait. I’m not sure I follow. You just told me you found a page called http://digg.com/asdfffffffffsdf which is located here http://digg.com/error but when I try to fetch that it returns HTTP 404.
If I were a robot I would be very confused.
I assume they’re doing this because they want to return a custom error page. This is not the right thing to do. You should configure Apache to serve a custom HTML page for your 404s.
Even caching HTTP servers can implement this.