🚀 go-pugleaf

Hi,

I am looking into the possibility of using Squid in combination with a URL
redirector in front of a number of IIS servers with private IP addresses.

Our current setup is based on an MS 2.0 Proxy that is publishing a number of
websites to the internet, and is also serving as a proxy server to the
internal LAN.

We will soon be moving the webservers to a DMZ protected by a 2.4/iptables
linux box. However, because of a lack of internet IP addresses, many
websites will still be *virtually* housed on the same IP address (ie. the
address of the firewall). Hence I find myself in need of a reverse proxy
capable of interpreting HTTP host headers and proxying traffic to various
protected 172.16.0.0 servers accordingly.

The following web page mentions a number of URL redirectors for Squid, some
of which appear to be very interesting (other seem to be aimed at content
blocking, which is not what I'm after):

http://mail.linuxmall.com/squid/related-software.html

My questions are:

- Do you have any experience with any of these, any preferences ? I am
particularly interested in Squirm, JesRed, or Squidgard. (Note that Security
& speed are major concerns - hence I don't think that a perl script based
redirector-1.1 will be up for the job). Which one do you prefer ?
- I don't intend to do any actual caching since there are no performance
problems on the webservers, only a shortage of IP addresses. Should I
reconsider ?
- Proxying of HTTPS requests must be possible.
- The firewall will probably not be used as a regular proxy server for the
internal LAN. However, if I wanted to do this in the future, is it possible
to combine the publishing feature (this is MS Proxy 2.0/ISA server
terminology) with regular proxying for the LAN ?
- Would it be a smart move to run two copies of squid on a host: a regular
proxy for the LAN and a reverse proxy for the webservers ?
- Are there any non Squid-based options I should consider ?

Thanks in advance,
Filip