Cache Peering allows web page caches to be shared among more than one server. This will improve performance and decrease bandwidth usage to the web. Cache Peering works between two EnGarde servers, but may work with other proxy servers that use ICP.
Cache Peering allows a server to handle a users request, check to see if it has the request URL cached and if not pass it on to the next peered server. If the next peered server has what the user is asking for it will return the response back to the original peered server. Then the original peered server will hand the results over to the user. Only if the page isn't cached among those servers will it be retrieved from the web. This method greatly increases the speed at which pages can be displayed to the user while reducing the overall bandwidth.
To define a peer server select Cache Peering from the Proxy Management screen.
Select New Peer to define the peer. You will need to know the server's IP address, hostname and the ports it runs its proxy server and ICP on so that you can properly define the server.
When all entries have been filled in selecting Define Peer will create the peer and it will appear on the main Cache Peering section. You can edit or delete your defined peer(s) by clicking on the highlighted name.
If the other server is also running the Guardian Digital IAM server user the default Proxy Port (8080) and ICP Port (3130) when configuring it.
Assuming the peer you defined is configured correctly cache peering will now work between the EnGarde server and the defined peer.