Some files in the
under the Apache distribution directory tree are provided as an
example to those that wish to write modules that use the Apache
The main file is
illustrates all the different callback mechanisms and call
syntaxes. 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:
- Make the server (run "
To add another module of your own:
cp modules/experimental/mod_example.c modules/new_module/mod_myexample.c
- Modify the file.
- Copy APACHE_MODULE line with "example" from
- Replace the first argument "example" with myexample.
- Replace the second argument with brief description of your module.
It will be used in
- If your module needs additional C compiler flags, linker flags or
libraries, add them to CFLAGS, LDFLAGS and LIBS accordingly.
config.m4files in modules directory for examples.
module/new_module/Makefile.in. If your module doesn't need special build instructions, all you need to have in that file is
- Run ./buildconf from the top-level directory.
- Build the server with --enable-myexample
To activate the example module, include a block similar to
the following in your
As an alternative, you can put the following into a
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.
|说明||Demonstration directive to illustrate the Apache module API|
|作用域||server config, virtual host, directory, .htaccess|
Example directive just sets a demonstration
flag which the example module's content handler displays. 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. The effect of this
directive one can observe under the point "
directive declared here: YES/NO".