[Solved] error pages

[sircamel]

hello,

 

webserver log says all the error pages (400.shtml/404.shtml and so on) are missing ... shouldn't there be a default set of error pages? ;-)

 

by the way: the search of the forum is totally broken and returns either 1000 unrelated things or nothing ;-)

 

camel

 

not really useful ;-)

 

[Mon Sep 06 17:58:32 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

[Mon Sep 06 17:53:45 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

[Mon Sep 06 17:53:44 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

[Mon Sep 06 17:53:44 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

[Mon Sep 06 17:53:36 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

[Mon Sep 06 17:46:34 2010] [error] [client 80.108.43.130] File does not exist: /home/omfgwdm/public_html/500.shtml

 

 

hmmm ... so why no hardcoded errors? :-)

 

In the event of a problem or error, Apache can be configured to do one of four things,

 

1. output a simple hardcoded error message

2. output a customized message

3. redirect to a local URL-path to handle the problem/error

4. redirect to an external URL to handle the problem/error

 

The first option is the default, while options 2-4 are configured using the ErrorDocument directive, which is followed by the HTTP response code and a URL or a message.

 

also my scripts fail to work randomly ... then i get a HTTP-500 status for like 30 minutes!?

[Byron]

This support request is being escalated to our root admin.

[Ashoat]

Yeah, the search sucks. And no, we don't have default error pages, and we don't plan on having them. We're offering you a raw, configurable hosting environment.