On Sat, 2004-01-17 at 20:47, Paul Mackinney wrote:
> Thanks very much, I'll google for the hack. The Debian bug db came up
> empty on this issue, maybe it's an apache bug?
Whoops! I renamed the working apache2-doc file and left it in
/etc/apache2/conf.d/, so it was being used after all. Add this
Gary Sandine declaimed:
> On Sat, 2004-01-17 at 11:33, Paul Mackinney wrote:
> > But the manual
> > foobar should be working by default...
>
> What versions of apache2 packages are you using? I used to have this
> problem, too, and there was a hack for /etc/apache2/conf.d/apache2-doc
> that fixed
On Sat, 2004-01-17 at 11:33, Paul Mackinney wrote:
> But the manual
> foobar should be working by default...
What versions of apache2 packages are you using? I used to have this
problem, too, and there was a hack for /etc/apache2/conf.d/apache2-doc
that fixed this. I removed the hack to the file
Richard Lyons declaimed:
> On Saturday 17 January 2004 09:26, Paul Mackinney wrote:
> > Hi,
> >
> > I'm doing a little webserver testing on a Sarge system, and right
> > away I find the following two problems with apache2:
> >
> > 1. cgi scripts don't run.
> >
> > Specifically, invoking either of t
On Saturday 17 January 2004 09:26, Paul Mackinney wrote:
> Hi,
>
> I'm doing a little webserver testing on a Sarge system, and right
> away I find the following two problems with apache2:
>
> 1. cgi scripts don't run.
>
> Specifically, invoking either of the two test scripts, printenv and
> test-cg
Hi,
I'm doing a little webserver testing on a Sarge system, and right away I
find the following two problems with apache2:
1. cgi scripts don't run.
Specifically, invoking either of the two test scripts, printenv and
test-cgi, results in their source being displayed. One is a perl script
and one
6 matches
Mail list logo
