Trickey configuration for cgi-scripts

Trickey configuration for cgi-scripts

Post by Brian Pollac » Wed, 20 Jan 1999 04:00:00

I'm trying to configure Apache so that any file ending in .t is executed as
a cgi script.  I can make this work fine when I create files ending in .t,
but here is the hard part.  The files won't actually exist, they are "false"
queries that the script will pull from a database.

For example:  should call
/usr/local/apache/code/scripter.cgi /html/index.t



1. apache: give /home/mailman/cgi-bin permissions to run cgi-scripts.

Hey ho,
I try to install mailman on my server.
Now I have to give /home/mailman/cgi-bin permissions to run cgi-scripts.
How can I do this?
In the documentation of mailman like
Exec          /mailman/*      $prefix/cgi-bin/*
ScriptAlias   /mailman/       $prefix/cgi-bin/

is shown. Which one is right, or none?


Some people have told me they don't think a fat penguin really embodies the
grace of Linux, which just tells me they have never seen a angry penguin
charging at them in excess of 100mph.  They'd be a lot more careful about
what they say if they had.  -- Linus Torvalds, announcing Linux v2.0

2. Question ab/ multiple producers/consumers

3. Configuration SEEMS Correct But CGI Scripts Won't Work

4. Enterprise server proble

5. Apache 1.3.4 configuration for cgi-bin/script directory specification

6. I need a good reference book!

7. /cgi-bin/phf /cgi-bin/test-cgi /cgi-bin/handler

8. ** Linux Documents Explained for Newbies ** Weekly Post

9. CGI-scripts and Apache

10. announce: cgi++ v2.0: a c++ library for cgi script handling

11. Accessing files as root in CGI-Scripts under Apache

12. Perl CGI script gets CGI params as ARGV arguments under Apache2

13. cgi-scripts -- archive??