1. Install Varnish

apt-get install varnish


2. Configure the backend (pico /etc/varnish/default.vcl)

backend default {
set backend.host = "157.166.224.26";
set backend.port = "80";
}


This will be the server containing the actual web site published to the users. I'm using the IP address for cnn.com for testing.

3. Configure deamon options for varnish to use the default.vcl (pico /etc/default/varnish)

Comment out the following lines: (lines 21 - 25)

#DAEMON_OPTS="-a :6081 \
# -T localhost:6082 \
# -b localhost:8080 \
# -u varnish -g varnish \
# -s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,1G"


Remove the comment blocks from these lines: (34 - 37)

DAEMON_OPTS="-a :6081 \
-T localhost:6082 \
-f /etc/varnish/default.vcl \
-s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,1G"


By default, Varnish listens on port 6081 as specified in the -a parameter but for production you probably want to use port 80.

4. Restart Varnish

/etc/init.d/varnish restart


5. Test by entering this location in a web browser: http://yourserver:6081.

Replace yourserver with your server's hostname or IP address

This is just a simple setup but you can set up multiple backends and do some advanced configurations. Here's the Varnish documentation

1. Install HAVP

apt-get install havp


2. Start HAVP if it didn't start after the installation

/etc/init.d/havp start


It's ready, by default HAVP listens on port 8080. You can configure your web browser to use the server as a proxy.

You can customize the error pages by editing the html files in this directory: /etc/havp/templates/en/

1. Install required packages

apt-get install build-essential autotools-dev debhelper libpcre3-dev zlib1g-dev libssl-dev


2. Receive the nginx source

apt-get source nginx


3. Enable the mail modules

cd nginx-x.x.x
pico debian/rules


Replace nginx-x.x.x with the correct folder created.

Add "--with-mail --with-mail_ssl_module" to the line starting with ./configure so that it looks something like this:

./configure $(CONFIGURE_OPTS) --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --http-log-path=/var/log/nginx/access.log --http-client-body-temp-path=/var/lib/nginx/body --http-proxy-temp-path=/var/lib/nginx/proxy --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --with-debug --with-http_stub_status_module --with-http_flv_module --with-http_ssl_module --with-http_dav_module --with-mail --with-mail_ssl_module


4. Build the package

dpkg-buildpackage


5. Install the new nginx package

dpkg -i ../nginx_x.x.x-x.deb


Replace nginx_x.x.x-x.deb with the correct version and platform. In my case the filename is: nginx_0.6.32-3+lenny3_amd64.deb

6. Configure nginx

Next step is to configure the nginx rules. That's outside the scope of this tutorial.

1. Install the Squid package

apt-get install squid


2. Allow your ip network to use the proxy server (pico /etc/squid/squid.conf). Append lines similar to these to your config

file:

acl mynetwork src 192.168.1.0/255.255.255.0
http_access allow mynetwork


Replace 192.168.1.0/255.255.255.0 with the network that should be able to use the proxy.

3. Don't forward client ip information (optional)

forwarded_for off


4. Restart the daemon

/etc/init.d/squid restart


5. Configure your web browser or application your would like to use the proxy server to connect to serverip at port 3128.

1. Install the pound package

apt-get install pound


2. Configure the load balancing. Replace everything below and including ListenHTTP with something like this: (pico /etc/pound/pound.cfg)

ListenHTTP
  Address 0.0.0.0
  Port 80
  xHTTP 0
 
  Service
    HeadRequire "Host: .*www.google.com.*"
 
    BackEnd
      Address 209.85.227.103
      Port 80
    End
    BackEnd
      Address 209.85.227.104
      Port 80
    End
    BackEnd
      Address 209.85.227.105
      Port 80
    End
    BackEnd
      Address 209.85.227.106
      Port 80
    End
  End
End


In this example we'll be listening for www.google.com and forward requests to 4 of Google's web servers/clusters. You can of course replace the domain with one of your own and point it to any servers. The servers can be on different networks, using different platforms and you can even forward different paths to different servers. Ex. www.google.com/apps could be forwarded to 1.2.3.4 while www.google.com is forwarded to 2.3.4.5. Click here for more details about Pound

3. Enable the Pound service (pico /etc/default/pound)

startup=1


4. Restart Pound

/etc/init.d/pound start


You must point the dns record for www.google.com to your server's IP address. You could use the hosts file to do this or use another domain.