Ok, here's the story. They tried telling me that I can't have a "cgi-bin" because it won't work. They said that is the same name as their system wide cgi-bin and all my requests would try to pull from THEIR cgi-bin. They wanted me to rename my folder to "cgibin", but I explained to them that I have about 40-50 scripts that work perfectly from MY cgi-bin. I sent them about 10 links and asked them why they all work if what they said was true. Here's their final response:
"Hmm, that's a good question. I was interested in finding out why it works that way also. I took a look through the Apache
documentation but couldn't find any reference to the behavior your website was experiencing. The Apache directive that controls the
location of the system wide CGI directory is called ScriptAlias. On our system we have this set as so:
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
This will direct all requests of www.domain.com/cgi-bin/ to the system path /var/www/cgi-bin/. Somehow though, your /cgi-bin
requests are working for scripts in your local cgi-bin folder. My guess is that Apache is confused somehow since the local cgi-bin
folder is conflicting with the ScriptAlias path. I even tried putting the following line in your VirtHost config for your
sierrasoho.org domain:
ScriptAlias /cgi-bin/ /home/biz/inkspinners/WWW/sierrasoho/cgi-bin/
But then no CGIs would run because the cgiwrapper cant find the cgiwrap program because we have changed the system location of
"cgi-bin" (cgiwrap is the program that lets you run CGI's as your user, not the web server). So unfortunately, it looks like the
only way to make your CGI's run is to change the name of your CGI directory."
Something doesn't make sense to me. But I guess I have no choice.
Thanks
