SummaryIf there is a web proxy in a network, there are additional condsiderations that must be taken into account for normal operation, as well as for edge cache.
OverviewA web proxy is used by many companies as a way to monitor and control the types of web traffic that go out, or as a NAT termination point for security reasons. If employing a proxy, there are considerations that need to be taken into account for general surfing as well as for edge cache, if applicable.
The most important thing to note in this type of scenarios is that most internet proxies out there are not transparent. They work as a network relay for all internet traffic from the users/hosts to the Web, but once the web requests arrive at the proxy, the internal IP for all these packets will be the IP of the proxy and not the hosts.
In this case, it is recommended to make sure the Exinda is located in the middle of the connection between the users and the proxy. This way, the reports will not be affected as Exinda will see all traffic sourced from the real IPs and not from the sole proxy's IP. Placing the exinda in the middle of the connection between the proxy and the internet will cause that all traffic is coming from a single internal address.
If implementing edge cache, there are further parameters that need to be configured:
1. Configure the Edge-cache Peers - Steps to configure Edge Cache Peer are found here - http://docs.exinda.com/ga-released/exos/6.4/PDFs/edge-cache.pdf (page 7)
- Use "8080" for HTTP Port and "0" for ICP port in the above configuration.
acceleration edge-cache application HTTP-ALT
3. Some users might also face issues with HTTPS traffic breaking after this solution. In this situation, perform the following command:
(config)# acceleration edge-cache never-direct