PICK A PAGE AND Home Site Guide Site Search Bulletin Board Virtual Greeting Cards -The Stuff You Want- Free CGI Script Archive Free Graphics Archive Free Coordinated Page Graphics -Getting Started on the Web- Clueless? For the Newbie! Domain Name Lookup Recommended Hosting Solutions Free Hosting -The Fun Tutorials- Lots of HTML Tricks and Tutorials HTML Tag Guide JavaScript Tricks and Tutorials Navigation Tricks Image Maps Tutorial -CGI, SSI and Unix Tutorials- SSI: Server Side Includes Forms Tutorial CGI Simple Tutorial Your First CGI Perl Script Banner Rotation Squawk: Recent News UNIX Guru Tutorial -Web Page Design Tutorials- Design Basics Most Important Part of your Page Photo Composition Tutorials MIDI Music on Your Pages All about COLOR THE SAFE Colors The Skinny on Fat Graphics Advanced Design Examples ASCII Chart -Managing Your Web Site- BNB on the APACHE Server Introduction to the Secure Server How to Promote Your Web Site Site Management Site Security Password Protection on Directories Site Diagnostics Script Troubleshooting -Resource Links- Offsite Resource Links Good Books The Tools You Need -All the Other Stuff- Newletter Back Issues Reader's Links Bird Droppings: Letters Kudos / Awards BNB FAQ Guestbook

Altering APACHE Error Messages Using the Text Method. The simplest method for changing the message that your readers see when they encounter an error is to modify the srm.conf file if you have the ability to do so, or to modify your .htaccess file. In the srm.conf file you will find a line that looks like this: #ErrorDocument 500 "The server made a boo boo. To change the error message for what is usually a script failure, change the line to read: ErrorDocument 500 "I am sorry that we inconvienced you with this error. The person responsible has been shot. Please note that you must use the " (quote) mark between the error number and the text. Do not include a closing quote. If you do not have access to the master system files, you can add the line as shown above to your .htaccess file. In order for this to work, the system administrator must make certain that the AllowOveride option called FileInfo is set. You should try to obtain AllowOveride All on your directories. You can of course have a special message for each error code: ErrorDocument 400 "Thank you for making a bad request. ErrorDocument 401 "You must have authorization to go here. ErrorDocument 403 "Hey, you can't go here. ErrorDocument 404 "Oh Toto, where is Toto? Have you seen Toto? ErrorDocument 500 "Managing programmers is like herding cats.

Find or Give Help on the BBS
Home Top E-Mail
If it looks great, it's by Christine

---