Revision: 14297 Author: adrian.chadd Date: Fri Sep 11 14:18:27 2009 Log: Created wiki page through web user interface. http://code.google.com/p/lusca-cache/source/detail?r=14297
Added: /wiki/FeatureCachePeers.wiki ======================================= --- /dev/null +++ /wiki/FeatureCachePeers.wiki Fri Sep 11 14:18:27 2009 @@ -0,0 +1,26 @@ +#summary How Squid/Lusca can be forced to use specific upstreams to relay requests +#labels Feature + += Introduction = + +Lusca has a very powerful and flexible method for building complex networks of HTTP proxies and upstream servers. These can be used to build both forward proxy networks and reverse proxy / content delivery networks. + += Overview = + +[TODO] + += Options = + +The general options are documented in squid.conf.default. + += Differences to Squid = + + * In the case of a fully transparent interception proxy (eg tproxy), upstream peers may or may not need to have the client IP address spoofed. In this case, the option "no-tproxy" forces connections to the cache peer to use the traditional outbound IP address selection versus the client spoofed address. + += Examples = + +[TODO] + += Implementation Details = + +[TODO] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "lusca-commit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/lusca-commit?hl=en -~----------~----~----~----~------~----~------~--~---
