If you're already a programmer,CGI is extremely straightforward, and just three resources should get you up to speed in the time it takes to READ them:

1. Installation NOTES for your HTTPD.Is it configured to run CGI scripts, and if so how does it identify that a URL should be EXECUTED? (Check your manuals, READMEs, ISP webpages/FAQS, and if you still can't find it ask your server administrator).
2. The CGI specification at NCSA tells you all you need to know to get your programs running as CGI applications.
3. WWW Security FAQ. This is not required to 'get it working', but is essential READING if you want to KEEP it working!

If you're NOT already a programmer, you'll have to learn. If you would find it hard to write, say, a 'grep' or 'cat' utility to run from the commandline, then you will probably have a hard time with CGI. Make sure your programs work from the commandline BEFORE trying them with CGI, so that at least one possible source of errors has been dealt with.

If you're already a programmer,CGI is extremely straightforward, and just three resources should get you up to speed in the time it takes to read them:

If you're NOT already a programmer, you'll have to learn. If you would find it hard to write, say, a 'grep' or 'cat' utility to run from the commandline, then you will probably have a hard time with CGI. Make sure your programs work from the commandline BEFORE trying them with CGI, so that at least one possible source of errors has been dealt with.