On Wed, Aug 4, 2010 at 10:04 AM, Kyle Bader <firstname.lastname@example.org> wrote:
>> AddHandler cgi-script cgi py
> Thanks, Kyle, you've been getting me closer and closer.
> If I'm starting to "get" the new stuff, AddHandler declares certain
> extensions.* Up until last month, extensions were not required, and in fact
> my CGI programs have never had them.* It used to be enough to use
> ScriptAlias, and put an executable in the directory.* If it was a script
> with a shebang, or a compiled ELF program all was well.* If I were going to
> use extensions, it would be .py or possibly .python, not .cgi or .pl.
I totally meant to have it be py instead of pl, I guess pounding away
at perl all day yesterday warped my mind.
It can have that effect
As near as I can tell from the logs, my problems started during a re-emerge of
apache, not a new version (reasons unknown -- portage seems to be doing that
more than I'm used to). * I've started to wonder if I didn't just screw up the usual
config file stuff I do with dispatch-conf, not realizing zapping the new would be
best.* Anyway, I'm going to be exploring.
Do you have cgi working on apache2 (2.2.15), and if so, how things are arranged?
I'll be trying to make a cgi out of a hello world in C, to see if my current config
can CGI at all.* If not, I'll be trying to back out config changes.** What a mess!
Kevin O'Gorman, PhD