Jeff Pang wrote:
vhA's programs are running under /path/a/cgi-bin, but actually, the programs of
vhA can access vhB's directory (ie,they can open and write some files in
/path/b/). vice versa, the programs of vhB can access vhA's directory.
It's not really a mod_perl thing but you need to
On Jan 11, 2008 10:57 PM, Jeff Pang <[EMAIL PROTECTED]> wrote:
> I met a strange requirement that, given Apache has two virtual hosts, vhA and
> vhB, vhA's document root is: /path/a/; vhB's document root is: /path/b/.
>
> vhA's programs are running under /path/a/cgi-bin, but actually, the programs
-Original Message-
>From: Roberto C. Sánchez <[EMAIL PROTECTED]>
>
>I prefer to run multiple httpd processes on high numbered ports (one for
>each site), then have the main httpd on port 80 do proxypass
>proxypassrever and name-based vhosting. Then you can also customize
>each httpd to o
On Fri, Jan 11, 2008 at 11:24:00PM -0500, Colin Wetherbee wrote:
>
> How about suexec? I used it quite some time ago, and it was awful to
> use, but it got the job done.
>
> http://httpd.apache.org/docs/2.2/mod/mod_suexec.html
>
> http://httpd.apache.org/docs/2.2/programs/suexec.html
>
I pre
Jeff Pang wrote:
I met a strange requirement that, given Apache has two virtual hosts,
vhA and vhB, vhA's document root is: /path/a/; vhB's document root
is: /path/b/.
vhA's programs are running under /path/a/cgi-bin, but actually, the
programs of vhA can access vhB's directory (ie,they can open
Hello,
I met a strange requirement that, given Apache has two virtual hosts, vhA and
vhB, vhA's document root is: /path/a/; vhB's document root is: /path/b/.
vhA's programs are running under /path/a/cgi-bin, but actually, the programs of
vhA can access vhB's directory (ie,they can open and writ
