Common Gateway Interface (CGI) provides a method for Web servers to interact with external content-generating programs, which are often referred to as CGI programs or CGI scripts. It is the one of the simplest methods for adding dynamic content to your Web site.
Using Apache Manager, you can control how Apache finds the interpreter used to run CGI scripts. For example, if you specify sys:\foo.nlm as the path and .foo as the extension, all CGI script files with a .foo extension are passed to the foo interpreter (foo.nlm).
The CGI Extensions page in Apache Manager enables you add CGI extensions to your Web server.
Figure 4-4 Apache CGI Extensions
To define CGI extensions:
In the
field, specify the complete path to an interpreter used to run CGI scripts.On NetWare, you need to create an NLMâ„¢ that can serve as your CGI interpreter. Writing an NLM requires programming knowledge. If you are a developer, visit the Novell Developer Web site at http://developer.novell.com.
In the
column, type the extension Apache should recognize as a CGI file.The default extension is .cgi.
Click
.Click
> to save your changes.or
Click
> to save your changes and restart Apache so your changes are immediately put into effect.For information about where configuration information is stored, see Section 2.3.3, Saving Configuration Changes and Restarting Apache in Apache Manager.
To edit a defined CGI path and extension:
Click
in the row of the CGI extension you want to modify.If there are no CGI extensions listed below the
section, none have yet been defined. Define one following the instructions above.Change the extension as needed.
Click
> to save your changes.or
Click
> to save your changes and restart Apache so your changes are immediately put into effect.For information about where configuration information is stored, see Section 2.3.3, Saving Configuration Changes and Restarting Apache in Apache Manager.
To remove a CGI extension:
Click
in the row of the CGI extension that you want deleted.Click
.Click
> to save your changes.or
Click
> to save your changes and restart Apache so your changes are immediately put into effect.For information about where configuration information is stored, see Section 2.3.3, Saving Configuration Changes and Restarting Apache in Apache Manager.
For a more thorough discussion of CGI on Apache, see Apache Tutorial: Dynamic Content with CGI on the Apache.org Web site.