Be sure to mark your CGI script executable. To do this telnet to he.net, log in, move to your cgi-bin by typing "cd cgi-bin", and then mark your script executable by typing "chmod 755 demo.cgi".
Be sure to transfer your script with your FTP client in text mode if it is a perl, tcl, or shell script. This will ensure the end of line characters are translated appropriately. Unix uses LF (linefeeds) to indicated the end of lines, the Mac uses CR (carrige returns), and DOS uses CR LF pairs at the end of lines.
suid is installed in the master cgi-bin of the server and allows you to invoke your CGI scripts. Your CGI scripts are run with your user id and have access to all of the files you have access to. suid expects your CGI scripts to be in a directory named cgi-bin in your home directory.
To invoke nph (non parsed header) CGI scripts use nph-suid instead.
<href="http://servername/cgi-bin/suid/~jdoe/demo.cgi">my
script</a>
This link first makes use of suid and then specifies the user cgi-bin and script to run by the /~jdoe/demo.cgi appended after it.
If your CGI script is a compiled program (for example, one written in C) you must keep the source on the server.
Your CGI script must not create performance problems on the server. Simple guidelines for what is reasonable is the load imposed by imagemap or cgiemail.
Because your scripts run as you they have the potential to create, modify, or delete files in your home directory. You are completely responsible for what they do. To protect youself avoid passing file names dynamically that the script will use to create, modify, or delete. In general, the safest CGI scripts are ones that only generate output. Next safest are ones that generate output and modify a specific file which is specified at compile time.
|
| Call 1-800-THE-LOST if you've seen this child. Click on the image for case details. We support the work of the National Center for Missing and Exploited Children.
Click Here To Add A Missing Child Link To Your Pages! |
|
|
|
Send E-Mail to: |
