Customizable responses can be defined to be activated in the event of a
server detected error or problem.
e.g. if a script crashes and produces a "500 Server Error" response, then
this response can be replaced with either some friendlier text or by a redirection to another URL (local or external).
Redirecting to another URL can be useful, but only if some information
can be passed which can then be used to explain and/or log the error/problem
more clearly.
To achieve this, Apache will define new CGI-like environment
variables, e.g.
REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap, image/jpeg REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05 9000/712) REDIRECT_PATH=.:/bin:/usr/local/bin:/etc REDIRECT_QUERY_STRING= REDIRECT_REMOTE_ADDR=121.345.78.123 REDIRECT_REMOTE_HOST=ooh.ahhh.com REDIRECT_SERVER_NAME=crash.bang.edu REDIRECT_SERVER_PORT=80 REDIRECT_SERVER_SOFTWARE=Apache/0.3 REDIRECT_URL=/cgi-bin/buggy.pl
note the REDIRECT_ prefix.
At least REDIRECT_URL and REDIRECT_QUERY_STRING will be passed to the new URL (assuming it's a cgi-script or a cgi-include). The other variables will exist only if they existed prior to the error/problem.
Here are some examples...
ErrorDocument 500 /cgi-bin/crash-recover ErrorDocument 500 "Sorry, our script seemed to crash because %s. Oh dear ErrorDocument 500 http://xxx/ ErrorDocument 404 /Lame_excuses/not_found.html ErrorDocument 401 /Subscription/how_to_subscribe.html
The syntax is,
ErrorDocument <3-digit-code> action
where the action can be,
ErrorDocument definitions are sensitive to a SIGHUP, so you can change any of the definitions or add new ones prior to sending a SIGHUP (kill -1)