From: wayne <wa...@ny...> - 2003-03-07 08:06:49
|
> From: M <m> > Subject: Transparent test > To: wayne <wa...@ny...> CC: pro...@sf... > Hey Wayne > That is the test: > C:\proxyTools>perl statProxy.pl -t all transparent > Extracting proxy strings, safeing, expanding/skipping ports, > validating, resolving, deduping... > 1 proxies to test (after processing) > ctrl-c to see results so far; double-ctrl-c to abort > Running test: 0 1 2 3 4 5 6 7 8 9 10 11 14 15 16 17 19 0.0.0.0:80 > statProxy v4.150 report from 217.xxxxx(UAE-dialup): > 0.0.0.0 :80 PFFFFFPPPPFP FPFP P 5.5/6.7 via:1.1 NC9 (NetCache NetApp > /5.2.1D8) agent:NetCache NetApp/5.3.1R1 From a UAE adsl box: 0.0.0.0 :80 PFFFFFPPFFFF FPFP F 2.8/7.2 via:1.1 NC9 (NetCache NetApp/5.2.1D8) agent:NetCache NetApp/5.3.1R1 > Reference page size was 14014 bytes > Wall clock time: 0.83 mins. > > Results have also been written to file statProxy.2003.3.6.0.out > I want to understand what is meant by transparent proxy? It's just a normal proxy, except that you don't need to connect to it directly. In the UAE case, it does nothing until it sees you connect to somewhere on port 80, and then it takes over. All HTTP commands it sees are executed by the proxy and never make it out to the web site you thought you were connected to. The fact that you don't need to connect to it, means you don't need to configure any proxy in your web browser. It also means that any tests you do using statProxy (or any other proxy tester) on port 80 are invalid. In my proxyTools, mergeHosts ignores such tests (and warns you) if it knows there is a transparent proxy in the connection, so that you don't stuff up your proxy databases. -- wa...@ny... http://proxytools.sourceforge.net/ |