First, make sure that the permissions on the file are set properly for execute permission. By default, the permissions are 644 (rw-r--r--) and do not allow execution. You need to change the permissions, or the mode, on your cgi script to 755 (rwxr-xr-x). Some FTP programs allow you to change file permissions, if yours doesn't, then you can use the File Manager in your Control Panel to change the permissions.

Many Expect scripts can be run directly with one change - the following line should be inserted before any other output: puts "Content-type: text/html\n" Next, make sure you invoke external programs using full paths. For example, instead of "spawn telnet", use "spawn /usr/ucb/telnet" (or whatever). Remember that the PATH and other environment variables are going to be different than what you are used to.

Unfortunately we cannot offer support for CGI scripting, so you will have to fix them on your own. You could start by doing a search on your favorite search engine (we recomment Google) for the error number or message you’re getting, and you might find some answers.

If you have a question and don't want to scroll through the list below, use this handy search thingy. If you don't find the answer to the question in the README file for the program, on the main information page for the program, or here, please drop us an email so we can add it to the list! Before you email me, please note that these scripts are not supported for sites on Tripod.com. For a free web hosting provider who supports CGI scripts, you can try HyperMart or Netfirms.com.

Name the CGI script using the extension cgi, for example myscript.cgi, and place it in the /var/www/cgi-bin/myusername directory. Make sure that the script has the appropriate permissions: it should be world-readable and world-executable (755). Test your script locally (from the shell) first, to make sure it compiles and runs without errors before it is run over the Web. Finally, point a browser to http://sulu.informatics.indiana.edu/cgi-bin/myusername/myscript.cgi.

This means that the script is failing before getting a chance to output any data. Look at the error log of your web server for any error output produced when the script is run, and see section 4.6 (above) for suggestions on what to do if your web server doesn't log meaningful error output.

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections.

This is a common error found in a Web browser when you are attempting to run a Perl or CGI script that has problems. The three most common reasons for this error are the following: Your script permissions are set wrong. Try setting them to 777 or 755 temporarily while troubleshooting the error. Your script was uploaded in binary file format instead of ASCII. You must upload Perl and CGI scripts in ASCII format only. Your path to Perl (the "sha bang" )line is wrong.

First check here (in Student Web Server Upgrade to Apache 1.3 ) to see if your problem is because of Apache 1.3 slightly silly directory permission requirements. If not, you can get hints about what's really going wrong by looking in /software/wwwapache-1.3_server/logs/error_log /software/wwwapache-1.3_server/logs/access_log /software/wwwapache-1.3_server/logs/cgi.

A CGI script is a special kind of text file that the server can run to perform various tasks, such as displaying a hit counter, or mailing a form to you which has been filled out by a customer. We offer 3 basic CGI scripts already installed and ready to run. You also have access to your own CGI-BIN directory where you can place your own scripts.

CGI scripts need to be set executable. You need to change the mode, or permissions, of your programs with your FTP program, and make them 755, or rwxr-xr-x. Note: A lot of scripts out there will tell you need to make them 775 or even 777. This is not good! It means anyone on the server can write to your script, and since its executable and executes as you, it could delete all your files.

For example, in the above paths, if your site is www.coloradomusic.org, "domain" refers to "coloradomusic.org".

You can register an account at [www.netfirms.com] or [www.spaceports.com]. FPG version 1.13 or higher will automatically kill the advertisting banner codes of Netfirms.

You trigger a server-side script by setting any object's URL. For example a frame, window, or an Image. An image will also "swallow" the data sent back by the server, so that they will not be visible anywhere. var dummyImage = new Image();dummyImage.src = "scriptURL.asp?param=" + varName; Mozilla (NN6.2+, Firefox, Ice Weasle etc), Opera 7.6+, Safari1.2+, the Windows version of IE versions 5+, and some other browsers provide the XML HTTP Request object.