[thelist] Tip: 3 Tips for HTTP Error documents

[Frank]

<tip type="HTTP Error Documents" author="Frank Marion">

When setting up an error document to handle Error 500, use a plain HTML 
document. Error "500 Internal Server Error" can sometimes mean "Your server 
side language (ie Coldfusion) isn't running.". Not much use if your error 
500 uses dynamic features.

</tip>

<tip type="HTTP Error Documents" author="Frank Marion">

One way to keep your plain HTML error documents up to date is to write a 
utility script that will create the correct .htaccess, and error documents. 
Whenever your site goes for a revamp, simply get it to regenerate the lot 
for you. This is especially useful if you keep to your standard 
conventions, such as including top and bottom templates.

Example. In your utility script create something like this

start file
         -- include template top
         -- error message here
         -- include template top
end file

write error doc file.

</tip>

<tip type="HTTP Error Documents" author="Frank Marion">

Don't try to create an Error 200 document. Error 200 means "No problem". 
Thus every successful load would send you to your 200 document. And each 
time it successfully loads, you would get it again--an infinite loop. Not 
very good for traffic.

</tip>


--
Frank Marion     lists at frankmarion.com      Keep the signal high.