This module is contained in the
modules/mod_example.c file, and
is not compiled in by default. It illustrates many of
the aspects of the
Apache 1.2 API
and, when used, demonstrates the manner in which module callbacks are
triggered by the server.
The files in the
src/modules/example directory under the
Apache distribution directory tree are provided as an example to those
that wish to write modules that use the Apache API.
The main file is
mod_example.c, which illustrates all
the different callback mechanisms and call syntaces. By no means does
an add-on module need to include routines for all of the callbacks -
quite the contrary!
The example module is an actual working module. If you link it into your server, enable the "example-handler" handler for a location, and then browse to that location, you will see a display of some of the tracing the example module did as the various callbacks were made.
To include the example module in your server, follow the steps below:
src/Configurationfile. If there isn't one, add it; it should look like this:
Module example_module modules/example/mod_example.o
src/Configurescript ("cd src; ./Configure"). This will build the Makefile for the server itself, and update the
src/modules/Makefilefor any additional modules you have requested from beneath that subdirectory.
To add another module of your own:
To activate the example module, include a block similar to the following in your srm.conf file:
<Location /example-info> SetHandler example-handler </Location>
As an alternative, you can put the following into a .htaccess file and then request the file "test.example" from that location:
AddHandler example-handler .example
After reloading/restarting your server, you should be able to browse to this location and see the brief display mentioned earlier.
Context: server config, virtual host, directory, .htaccess
The Example directive activates the example module's content handler for a particular location or file type. It takes no arguments. If you browse to an URL to which the example content-handler applies, you will get a display of the routines within the module and how and in what order they were called to service the document request.