mirror of
https://github.com/apache/httpd.git
synced 2025-12-24 15:01:03 +03:00
Thanks to Yoshiki, we seem to have an (at least temporary) solution to our
doc transformation problem. As the first step, I'm removing all the .html files. They will be replaced by language-specific files. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95238 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
@@ -1,95 +0,0 @@
|
||||
<html xmlns="http://www.w3.org/TR/xhtml1/strict"><head><!--
|
||||
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|
||||
This file is generated from xml source: DO NOT EDIT
|
||||
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|
||||
--><title>mod_example- Apache HTTP Server</title><link href="../style/manual.css" type="text/css" rel="stylesheet"/></head><body><blockquote><div align="center"><img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]"/><h3>Apache HTTP Server Version 2.0</h3></div><h1 align="center">Apache Module mod_example</h1><table cellspacing="1" cellpadding="0" bgcolor="#cccccc"><tr><td><table bgcolor="#ffffff"><tr><td valign="top"><span class="help">Description:</span></td><td>Illustrates the Apache module API</td></tr><tr><td><a href="module-dict.html#Status" class="help">Status:</a></td><td>Experimental</td></tr><tr><td><a href="module-dict.html#ModuleIdentifier" class="help">Module Identifier:</a></td><td>example_module</td></tr></table></td></tr></table><h2>Summary</h2>
|
||||
<blockquote><table><tr><td bgcolor="#ffe5f5">
|
||||
This document has not been updated
|
||||
to take into account changes made in the 2.0 version of the
|
||||
Apache HTTP Server. Some of the information may still be
|
||||
relevant, but please use it with care.
|
||||
</td></tr></table></blockquote>
|
||||
|
||||
<p>The files in the <code>src/modules/example directory</code>
|
||||
under the Apache distribution directory tree are provided as an
|
||||
example to those that wish to write modules that use the Apache
|
||||
API.</p>
|
||||
|
||||
<p>The main file is <code>mod_example.c</code>, which
|
||||
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!</p>
|
||||
|
||||
<p>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.</p>
|
||||
<h2>Directives</h2><ul><li><a href="#example">Example</a></li></ul><h2>Compiling the example module</h2>
|
||||
|
||||
<p>To include the example module in your server, follow the
|
||||
steps below:</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
Uncomment the "AddModule modules/example/mod_example" line
|
||||
near the bottom of the <code>src/Configuration</code> file.
|
||||
If there isn't one, add it; it should look like this:
|
||||
<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>
|
||||
AddModule modules/example/mod_example.o
|
||||
</code></td></tr></table></blockquote>
|
||||
</li>
|
||||
|
||||
<li>Run the <code>src/Configure</code> script
|
||||
("<code>cd src; ./Configure</code>"). This will
|
||||
build the Makefile for the server itself, and update the
|
||||
<code>src/modules/Makefile</code> for any additional modules
|
||||
you have requested from beneath that subdirectory.</li>
|
||||
|
||||
<li>Make the server (run "<code>make</code>" in the
|
||||
<code>src</code> directory).</li>
|
||||
</ol>
|
||||
|
||||
<p>To add another module of your own:</p>
|
||||
|
||||
<ol type="A">
|
||||
<li><code>mkdir src/modules/<em>mymodule</em></code></li>
|
||||
|
||||
<li><code>cp src/modules/example/*
|
||||
src/modules/<em>mymodule</em></code></li>
|
||||
|
||||
<li>Modify the files in the new directory.</li>
|
||||
|
||||
<li>Follow steps [1] through [3] above, with appropriate
|
||||
changes.</li>
|
||||
</ol>
|
||||
<h2>Using the <code>mod_example</code> Module</h2>
|
||||
|
||||
<p>To activate the example module, include a block similar to
|
||||
the following in your <code>srm.conf</code> file:</p>
|
||||
<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>
|
||||
<Location /example-info><br>
|
||||
SetHandler example-handler<br>
|
||||
</Location>
|
||||
</code></td></tr></table></blockquote>
|
||||
|
||||
<p>As an alternative, you can put the following into a <a href="core.html#accessfilename"><code>.htaccess</code></a> file
|
||||
and then request the file "test.example" from that location:</p>
|
||||
<blockquote><table cellpadding="10"><tr><td bgcolor="#eeeeee"><code>
|
||||
AddHandler example-handler .example
|
||||
</code></td></tr></table></blockquote>
|
||||
|
||||
<p>After reloading/restarting your server, you should be able
|
||||
to browse to this location and see the brief display mentioned
|
||||
earlier.</p>
|
||||
<hr/><h2><a name="Example">Example</a> <a name="example">Directive</a></h2><table cellpadding="1" cellspacing="0" border="0" bgcolor="#cccccc"><tr><td><table bgcolor="#ffffff"><tr><td><strong>Description: </strong></td><td>Demonstration directive to illustrate the Apache module
|
||||
API</td></tr><tr><td><a href="directive-dict.html#Syntax" class="help">Syntax:</a></td><td>Example</td></tr><tr><td><a href="directive-dict.html#Context" class="help">Context:</a></td><td>server config, virtual host, directory, .htaccess</td></tr><tr><td><a href="directive-dict.html#Status" class="help">Status:</a></td><td>Experimental</td></tr><tr><td><a href="directive-dict.html#Module" class="help">Module:</a></td><td>mod_example</td></tr></table></td></tr></table>
|
||||
<p>The <code class="directive">Example</code> 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 "<code>Example
|
||||
directive declared here: YES/NO</code>".</p>
|
||||
<hr/></blockquote><h3 align="center">Apache HTTP Server Version 2.0</h3><a href="./"><img src="../images/index.gif" alt="Index"/></a><a href="../"><img src="../images/home.gif" alt="Home"/></a></body></html>
|
||||
Reference in New Issue
Block a user