Jimmy George wrote:
<snip>
> An earlier email of mine did say that this cgi-bin folder in my home
> site is a 711 protection and does contain a file test1.cgi also at 711
> protection that does work.
>
711 should work as you say since you (the web server's user) are simply
executing the script.
> So that 500 error MAY be because I am running the script as a world
> member and trying to access local data that possibly only the user can
> permit access to? Yes/NO? Using a submit from a form loaded from the
> site does not change the situation though.
>
This would surprise me as accessing local data would return an error in
an open() call or in a system(), etc. which would be along the lines of
<permission denied>, etc. and would die at the open/system/etc. call and
not the whole script. The only time when this would cause a 500 error is
if it died loudly before the header was printed (HTTP 1.0 only?), or
prevented the header from printing at all.
Do you by chance have access to the error log for the web server as this
will usually provide more information, or have you tried running a local
copy of the cgi script through a local web server *so* that you can have
access to what the error message is?
- Are you certain all modules used in the script are available on the
server where the script is run?
- Have you syntax checked the script?
- Have you tried uploading a copy without use strict and use warnings
turned on? While these are good things to have on possibly they are
doing something pre-header that is causing the server to cough, if you
remove them, and it works, then at least you know where to start looking.
this might be a start.................
http://danconia.org
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
