Sun ONE proxy server

To debug the Sun ONE proxy server:

In the <SunOne>/<proxy_server_name>/logs/access directory, run:
```
tail -f <http_trace_file>
```
Where SunOne is the Sun ONE proxy server installation directory, proxy_server_name is the name of the proxy server that you configured during installation, and http_trace_file is the name of the proxy server’s HTTP trace file.

You should see output similar to the following, although the format can be configured by the system administrator:
```
10.22.84.155 -- hhsi2 [04/Sep/2003:16:15:23 -0700] 
"GET http://srd.yahoo.com:80/ HTTP/1.1" 200 38685 200 38685 -- ....
```
Where 10.22.84.155 is the IP address of the host that sent the HTTP request; for Enterprise Portal, this should always be the EP host name. The “GET <URL>” string is the HTTP request.

You can tell whether the proxy server is routing internal EP requests by the URL. If the URL is an EP servlet name, then we know the EP host name is not specified in the proxy.bypass property, and is therefore routed by EP to the proxy server. For example, if you see:
```
 GET <epHostName>:<ep port>/FWController ...
```
Where “FWController” is an EP servlet, then we know that EP is routing internal requests to the proxy server.If the EP host is on the bypass list, you do not see any HTTP requests in the proxy server’s HTTP trace file that include an EP host name, EP port number, or EP servlet in the URL.

For more help analyzing your system, see the Sun ONE Web Proxy Server Deployment Guide on the Sun Product Documentation Web page.