1.5.6 To Collect Debug Data on Web Proxy Server Protocol Problems

Use this task to collect data when Web Proxy Server 's functioning is not in conformance with an RFC.

1. Collect the general system information as explained in To Collect Required Debug Data for Any Web Proxy Server Problem.

2. Details of the RFC and the specific section that you believe the Proxy Server is not conforming to.

3. Check if the Proxy Server is displaying the same problem with a different browser. You can check in browsers like Internet Explorer, Mozilla, Netscape and so on.

4. Provide network trace files between components, such as these:

   • Browser and Proxy server

   • Proxy Server and Firewall

   • Proxy Server and Directory Server

   • Firewall and the Web

   Here are examples of commands on the proxy server side:

   Solaris

   snoop -V -vvv -d <interface> -o /tmp/proxy-snoop-web <IP_PROXY_SERVER>

   HP-UX

   tcpdump -i <interface> -w /tmp/proxy-snoop-web host <IP_PROXY_SERVER>

   ---

   Note –

   tcpdump for HP-UX is available at: http://hpux.connect.org.uk. You can also use the native command nettl.

   ---

   Linux

   tethereal -V -F snoop -i <interface> -w /tmp/proxy-snoop-web host <IP_PROXY_SERVER>

   ---

   Note –

   You can use the graphical user interface for tethereal or use the command tcpdump. tethereal is available at: http://www.ethereal.com.

   ---

   Windows

   tethereal -vvv -i <interface> -w /tmp/proxy-snoop-web host <IP_PROXY_SERVER>

   ---

   Note –

   You can use either the graphical user interface or the command for tethereal. tethereal is available at: http://www.ethereal.com.

   ---

   ---

   Note –

   Clearly indicate IP and hostname for each component. This will help to read the network trace files correctly .

   ---