Debugging your CGI scripts through Telnet.
One of the most powerful features of Telnet is that you can pinpoint problems in your CGI
scripts. Unlike the HTTPD protocol which displays the infamous "Internal Server
Error" message, telnet will tell you what is the real problem!
To test your script, you must execute it on the server which means your permissions must
allow you (the user) to execute the script. Otherwise, a permission denied message will
occur.
Telnet into the directory where the script you wish to test resides. Lets say that the CGI
script named "links.cgi" is giving us problems! To find the problem, type in
"./links.cgi". The server will then execute the script and tell you what, if any
problems occur. The syntax for this command is "./script_name".
After you have found the problem, you can edit your CGI script using PICO in Telnet, then
test it again. Eventually you will get your script working, and much faster than trying to
pinpoint the problem yourself!
Note: 95% of the time, the problem is either the permissions on the script(s) are not
properly set or the scripts(s) varible(s) are not properly set.