On 2009-12-19, Lars Nooden <lars.cura...@gmail.com> wrote:
> The vulnerable machines are still accessible via the proxy, squid.
> Don't fiddle with half measures, move what you have over to Apache.
> Say what you have the machine for and it will be easier to find the
> right software for you.

It could equally be "I have a webserver running apache, I want to split
vhosts onto separate (machines|httpd instances) and keep them on a single
IP address without using something which is total overkill".

And sometimes it's simply not possible to move things to a different
platform.

On 2009-12-19, Ben Calvert <b...@flyingwalrus.net> wrote:
> This is what squid is for.

Or www/pound, or www/varnish, or apache mod_proxy, or lighttpd mod_proxy, or...
pound is probably the simplest of these, but each have their advantages and
disadvantages.

On 2009-12-18, James Stocks <stoc...@stocksy.co.uk> wrote:
> I'm presently using Apache to reverse-proxy HTTP connections through to our
> Microsoft IIS servers so that we don't have to expose IIS directly to Internet
> hosts.  Recently, I've been testing relayd in this role.
>
> Apache can reverse-proxy requests for several internal HTTP servers through a
> single internet-routable IP address by using virtual hosts.  I've not yet
> discovered a way of getting relayd to forward the request to a different host
> depending on the content of the 'Host:' header.  Does relayd have this
> capability?  If so how do I do it?

It would make a lot of sense to be able to do this, but it doesn't seem
possible (if it actually is possible, it's very well hidden in the docs).

Reply via email to