On Mon, Sep 10, 2001 at 04:02:04PM -0400, Perrin Harkins wrote:
> > i've seen discussion at perl.apache.org/guide about having a
> > hefty mod_perl server with a lightweight server proxying
> > the heavy-lifting requests to the mod_perl server (same machine,
> > different machine).
> >
> > can this be done with mod_ssl and mod_perl?
>
> Yes, lots of people do that. You need the front-end to have mod_proxy and
> mod_ssl.
that makes sense.
> > internet firewall mod_ssl backend mod_perl
> > --------> [1.2.3.4] --------> [192.168.7.10]
> > :443 ssl verify -------> apache:80
> > :80 portforward ------> apache:80
> >
> > i'm thinking of using port forwarding on 1.2.3.4 to send :80 http
> > requests directly to the mod_perl server, and have :443 https
> > requests get verified thru the mod_ssl server which then also get
> > sent to the mod_perl server at 192.168.7.10 (HTML::Mason needed
> > to do the work).
>
> I suggest you have both go through the front-end server. There are multiple
> reasons to do this, which are outlined in the guide.
are you referring to the guide's 'scenarios' section where two
servers are cached via squid? it's over my head...
--
[EMAIL PROTECTED]
http://sourceforge.net/projects/newbiedoc -- we need your brain!
http://www.dontUthink.com/ -- your brain needs us!
