6.View the access log file on the Apache Proxy server. Messages similar to the following are contained in the file:

YOUR_WEB_BROSWER_IP - - [03/Feb/2007:13:30:48 -0500] "GET http://YOUR_WEB_SERVER_IP/test.html HTTP/1.0" 200 206 "-" "ApacheBench/2.0.40-dev"

View the access log file on the Apache HTTP server. Messages similar to the following are contained in the file:

YOUR_PROXY_SERVER_IP - - [24/May/2007:11:38:46 +0800] "GET /test.html HTTP/1.1" 200 206 "-" "ApacheBench/2.0.40-dev"

These messages verify that the Apache Proxy server configuration is successful.

Error Responses and Redirects

The following three types of error responses can be customized and are addressed in this section:

Plain text

Local URL redirect

External URL redirect

Customizing Plain Text Responses

The following is an example of how to customize a plain text error response:

1.Edit the following file:

/etc/apache2/errors.conf

In the preceding file, change (or add, if it does not exist already) the following line:

ErrorDocument 404 "The page you requested does not exist! Plain text example"

2.Restart your Apache HTTP server for the changes take effect.

3.Verify the custom text error message by opening a browser and entering the following website:

http://<YOUR_WEB_SERVER_IP>/non-exist

The following message appears:

The page you requested does not exist! Plain text example

Customizing Local URL Redirect Responses

The following is an example for customizing a local URL redirect error message:

1.Edit the following file:

/etc/apache2/errors.conf

In the preceding file, change (or add, if it does not exist already) the following line:

ErrorDocument 404 "/missing.html"

2.Create the following HTML file:

/srv/www/htdocs/missing.html

Add the following lines to the preceding file:

<HTML>

<HEAD>

</HEAD>

<BODY DIR="LTR">

<P ALIGN=CENTER STYLE="margin-bottom: 0cm"> <FONT FACE="Times New Roman, serif">

<FONT SIZE=6>The page you request does not exist! Local redirects example</FONT></FONT></P> </BODY>

</HTML>

Installing, Configuring, and Managing Web Server Middleware Stack Components 25