Differences between version 6 and revision by previous author of TransparentProxy.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
Newer page: | version 6 | Last edited on Monday, July 5, 2004 8:35:18 pm | by CraigBox | Revert |
Older page: | version 5 | Last edited on Sunday, March 7, 2004 4:11:19 pm | by JohnMcPherson | Revert |
@@ -1,5 +1,5 @@
-Transparent Proxying is when you use NetworkAddressTranslation to intercept traffic going to specific port and redirect it to go to a proxy. This is very popular in NewZealand [ISP]'s to redirect traffic to port 80 ([HTTP]) to a proxy
so they can attempt to proxy common content and save bandwidth (as all international traffic to/from NewZealand carries charges). The flaw in this plan is that while the proxy is supposed to be transparent (ie: you're not supposed to be able to tell it's there), far too often it becomes opaque, and you can tell that it's there. Common problems with Transparent proxies:
+Transparent Proxying is when you use NetworkAddressTranslation to intercept traffic going to specific port and redirect it to go to a proxy. This is very popular in NewZealand [ISP]'s to redirect traffic to port 80 ([HTTP]) to a WebProxy,
so they can attempt to proxy common content and save bandwidth (as all international traffic to/from NewZealand carries charges). The flaw in this plan is that while the proxy is supposed to be transparent (ie: you're not supposed to be able to tell it's there), far too often it becomes opaque, and you can tell that it's there. Common problems with Transparent proxies:
* The source address is no longer your machine but the proxy, so any website that uses IP based authentication won't work.
* The source address may come from different IP's every time you request a page, so any website that remembers what IP your on and requires you to login each time you change it will ask you to login again always, sigh.
* The TransparentProxy accepts the connection, gets the request *then* goes and finds out if the page is available, so your browser doesn't get to handle events such as "Connection Timed out" or "Connection Refused"