RE: [us...@httpd] Locking down a proxy server

2009-03-23 Thread David Vaughan
> From: Krist van Besien [mailto:krist.vanbes...@gmail.com] > While apache can be used as a general web proxy it is not the best > suited program for this. > > I'd look in to squid. You can install squid on all your local office, > and configure it to use the central office as a "parent" cache. Sq

Re: [us...@httpd] Locking down a proxy server

2009-03-23 Thread Krist van Besien
On Mon, Mar 23, 2009 at 10:28 AM, David Vaughan wrote: > As the local offices are international I was reluctant to employ SSL > technology > because of the associated import/export restrictions.  Also, I'm not > sure why you > emphasise not to use Apache. While apache can be used as a general we

RE: [us...@httpd] Locking down a proxy server

2009-03-23 Thread David Vaughan
Davide Bianchi wrote: >Use your local firewall to implement a transparent proxy, configure each >local proxy to forward his request to the main proxy on a special port, >filter on the main proxy with that port only and implement certificate >authentication between the local and the central proxy.

Re: [us...@httpd] Locking down a proxy server

2009-03-23 Thread Davide Bianchi
David Vaughan wrote: > I have a number of networks (think of them as being in local offices), > each of which is connected to the internet via a NAT'ed firewall. Users > on these networks access the internet via an Apache server acting as a > forwarding proxy. These local office proxies are then c

[us...@httpd] Locking down a proxy server

2009-03-23 Thread David Vaughan
I have a number of networks (think of them as being in local offices), each of which is connected to the internet via a NAT'ed firewall. Users on these networks access the internet via an Apache server acting as a forwarding proxy. These local office proxies are then chained to a single central f