2006 Dec 7

Redirecting 404 errors

we could redirect our users from a 404 error page not found to any url by editing our .htaccess files. this is usefull to give us more control in handling vairous html error codes. using the ErrorDocument tag and specifying the error code 404 as the page not found error code, (other error code might also be used in the redirect like: 400 - Bad Syntax, 401 - Unauthorized, 402 - Not used, 403 - Forbidden, 404 - Not Found, 500 - Internal Error, 501 - Not Implemented, 502 - Overloaded, 503 - Gateway Timeout).

Redirecting to an error page:

ErrorDocument 404 /404.html
- redirects the user to the 404.html page

using Rewrite to do the redirect:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule (.+) http://www.tildemark.com/404page/$1

or

RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.+)testing\.html?$ temporary/$1

Display an html page:

ErrorDocument 404 <b>Page Not Found</b><p /><br /><a href="http://www.tildemark.com">Tildemark blogs homepage</a>

0 TrackBacks

Listed below are links to blogs that reference this entry: Redirecting 404 errors.

TrackBack URL for this entry: http://www.tildemark.com/cgi-bin/mt4/mt-tb.cgi/43

3 Comments

Wait until you read this article that shows every single Apache Status Code and the actual headers and src returned from that error! Force Apache to output any HTTP Status Code with ErrorDocument

I setup an automated system to view all 57 Apache Response codes and ErrorDocuments, saving the headers and returned content for future reference. Use this page as a reference when designing scripts that use headers. Ex: 404 Not Found, 200 OK, 304 Not-Modified, 506 Service Temporarily Unavailable, etc.

When a Status code is encountered, Apache serves the header and the ErrorDocument for the error code. So if you can see any Header and ErrorDocument by causing that error on Apache.

For instance, if you request a file that doesn’t exist, a 404 Not Found is issued and the corresponding ErrorDocument is served with the 404 Not Found Header. So we can see what Apache 404 Errors and Response Codes look like, but how do we cause errors for the 56 other Apache Response Codes?

whoaaaa. that list is great! but isn't it too overkill? just didn't think of the other 56 error codes.

thanks anyway, this is indeed useful in my future venture with apache. :D

I live for overkill!

My whole blog is full of articles that are definately overkill. :p

Leave a comment

About this Entry

This page contains a single entry by tildemark published on December 7, 2006 7:16 AM.

transparent images using css with opacity was the previous entry in this blog.

Tableless form using HTML with CSS is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Recent Activity

Friday

  • tildemark tweeted, "im so sleepy. Zzzzzzzz"

Sunday

  • tildemark tweeted, "some of my scipts are not working with godaddy. but works fine on the others. not mention their poorly coded admin page"

Today

  • tildemark tweeted, "so many pending tasks i need to finish. need more coffee !!!"
  • tildemark tweeted, "@gmtristan i dont think that is true."

Today

  • tildemark tweeted, "how does godaddy subdomain behaves? i have some problems with it on my scripts. it does not seem to accept query strings.."

Monday

  • tildemark tweeted, "i had a hard time removing the error messages generated by surf side kick. i ended up uninstalling most of my applications."

Sunday

  • tildemark tweeted, "i got hit by surf side kick and im getting numerous error messages on my screen. tskkkkk"

Saturday

  • tildemark tweeted, "check boxes, i didn't know they can also be complex"
  • tildemark tweeted, "this smart bro internet speed is depressing, i thinking of filling a complaint to the DTI next week."

Friday

  • tildemark tweeted, "the seminar turned out to be leadership training. it was fun, learned alot. i have already attended numerous seminars but this is different."