diff options
| author | Jason McIntyre <jmc@cvs.openbsd.org> | 2005-07-29 09:37:46 +0000 |
|---|---|---|
| committer | Jason McIntyre <jmc@cvs.openbsd.org> | 2005-07-29 09:37:46 +0000 |
| commit | 6c438554db4c1b392347c9bc8178a1c7654def54 (patch) | |
| tree | fabc1caf33510b73f7197890b392dfbfd980c926 /usr.sbin/httpd/htdocs | |
| parent | 6624590b49e420eb3d99056bb00bdf4839063672 (diff) | |
from tamas tevesz:
==> some more alien platforms and obsolete info. the mod/core.html
change is because 1) the target link doesn't exist, 2) it
probably was meant to refer to misc/known_bugs.html in the
first place, which just got removed.
thanks henning for guidance.
Diffstat (limited to 'usr.sbin/httpd/htdocs')
18 files changed, 0 insertions, 2138 deletions
diff --git a/usr.sbin/httpd/htdocs/manual/index.html.html b/usr.sbin/httpd/htdocs/manual/index.html.html index 85406dd286b..e19b0ebe715 100644 --- a/usr.sbin/httpd/htdocs/manual/index.html.html +++ b/usr.sbin/httpd/htdocs/manual/index.html.html @@ -100,11 +100,6 @@ </tr> <tr> - <td><a href="install.html">Compiling and - Installing</a> </td> - </tr> - - <tr> <td><a href="invoking.html">Starting</a> </td> </tr> diff --git a/usr.sbin/httpd/htdocs/manual/install.html.html b/usr.sbin/httpd/htdocs/manual/install.html.html deleted file mode 100644 index 514d5d3c0d8..00000000000 --- a/usr.sbin/httpd/htdocs/manual/install.html.html +++ /dev/null @@ -1,417 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Compiling and Installing Apache</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#000080" - alink="#FF0000"> - <div align="CENTER"> - <img src="images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server</h3> - </div> - - - - <h1 align="CENTER">Compiling and Installing Apache 1.3</h1> - - <ul> - <li><a href="#download">Downloading Apache</a></li> - <li><a href="#intro">Introduction</a></li> - <li><a href="#apaci">Installing the Apache 1.3 HTTP server with APACI</a></li> - <ul> - <li><a href="#requirements">System requirements</a></li> - <li><a href="#configure">Configuring the source tree</a></li> - <li><a href="#build">Building the package</a></li> - <li><a href="#installing">Installing the package</a></li> - </ul> - <li><a href="#traditional">Building and installing the traditional way</a></li> - <ul> - <li><a href="#trad_configure">Configuring the installation</a></li> - <li><a href="#trad_compile">Compiling Apache</a></li> - <li><a href="#trad_install">Installing Apache</a></li> - </ul> - <li><a href="#testing">Testing the package</a></li> - <li><a href="#time">Set your system time correctly</a></li> - </ul> - - <h2><a id="download" name="download">Downloading Apache</a></h2> - - <p>You may download the latest version of Apache either directly from the - <a href="http://httpd.apache.org/download.cgi">Download Page</a>.</p> - - <h2><a id="intro" name="intro">Introduction</a></h2> - - <p>Like all good things, there are two ways to configure, compile, and - install Apache. You can go for the 3-minute installation process using - the APACI process described below; or, you can opt for the same mechanism - used in previous versions of Apache, as described in the file - 'src/INSTALL'. Each mechanism has its benefits and drawbacks - APACI is - newer and a little more raw, but it gets you up and running the least - amount of time, whereas the "Configuration.tmpl" mechanism may be more - familiar and give you some more flexibility to the power user. We'd be - very interested in your comments and feedback regarding each - approach.</p> - - <h2><a id="apaci" name="apaci">Installing the Apache 1.3 HTTP server with - APACI</a></h2> - - <h3>Overview for the impatient</h3> -<pre> - $ ./configure --prefix=PREFIX - $ make - $ make install - $ PREFIX/bin/apachectl start -</pre> - - <p><b>NOTE:</b> <code>PREFIX</code> is not the string "PREFIX". Instead - use the Unix filesystem path under which Apache should be installed. For - instance use "<code>/usr/local/apache</code>" for PREFIX above.</p> - - <h3><a id="requirements" name="requirements">Requirements</a></h3> - - <p>The following requirements exist for building Apache:</p> - - <dl> - <dt><b>Disk Space:</b></dt> - - <dd>Make sure you have approximately 12 MB of temporary free disk space - available. After installation Apache occupies approximately 3 MB of - disk space (the actual required disk space depends on the amount of - compiled in third party modules, etc).</dd> - - <dt><b>ANSI-C Compiler:</b></dt> - - <dd>Make sure you have an ANSI-C compiler installed. The GNU C compiler - (GCC) from the Free Software Foundation (FSF) is recommended (version - 2.7.2 is fine). If you don't have GCC then at least make sure your - vendors compiler is ANSI compliant. You can find the homepage of GNU at - http://www.gnu.org/ and the GCC distribution under - http://www.gnu.org/order/ftp.html .</dd> - - <dt><b>Perl 5 Interpreter [OPTIONAL]:</b></dt> - - <dd>For some of the support scripts like `apxs' or `dbmmanage' (which - are written in Perl) the Perl 5 interpreter is required (versions 5.003 - and 5.004 are fine). If no such interpreter is found by APACI's - `configure' script this is no harm. Of course, you still can build and - install Apache 1.3. Only those support scripts cannot be used. If you - have multiple Perl interpreters installed (perhaps a Perl 4 from the - vendor and a Perl 5 from your own), then it is recommended to use the - --with-perl option (see below) to make sure the correct one is selected - by APACI.</dd> - - <dt><b>Dynamic Shared Object (DSO) support [OPTIONAL]:</b></dt> - - <dd> - <p>To provide maximum flexibility Apache now is able to load modules - under runtime via the DSO mechanism by using the pragmatic - dlopen()/dlsym() system calls. These system calls are not available - under all operating systems therefore you cannot use the DSO - mechanism on all platforms. And Apache currently has only limited - built-in knowledge on how to compile shared objects because this is - heavily platform-dependent. The current state is this:</p> - - <ul> - <li> - Out-of-the-box supported platforms are: - - <p> - <table border="0"> - <tr> - <td>Linux</td> - <td>SunOS</td> - <td>UnixWare</td> - <td>Darwin/Mac OS</td> - </tr> - <tr> - <td>FreeBSD</td> - <td>Solaris</td> - <td>AIX</td> - <td>OpenStep/Mach</td> - </tr> - <tr> - <td>OpenBSD</td> - <td>IRIX</td> - <td>SCO</td> - <td>DYNIX/ptx</td> - </tr> - <tr> - <td>NetBSD</td> - <td>HPUX</td> - <td>ReliantUNIX</td> - <td>BSDI</td> - </tr> - <tr> - <td>Digital Unix</td> - <td>DGUX</td> - </tr> - </table> - </p> - </li> - - <li> - Entirely unsupported platforms are: - - <p>Ultrix</p> - </li> - </ul> - - <p>If your system is not on these lists but has the dlopen-style - interface, you either have to provide the appropriate compiler and - linker flags (see CFLAGS_SHLIB, LDFLAGS_SHLIB and - LDFLAGS_SHLIB_EXPORT below) manually or at least make sure a Perl 5 - interpreter is installed from which Apache can guess the options.</p> - - <p>For more in-depth information about DSO support in Apache 1.3 - please read the document htdocs/manual/dso.html carefully. Especially - the section entitled "Advantages & Disadvantages" because using - the DSO mechanism can have strange side-effects if you are not - careful. BE WARNED!</p> - </dd> - </dl> - - <h3><a name="configure">Configuring the source tree</a></h3> - - <p>The next step is to configure the Apache source tree for your - particular platform and personal requirements. The most important setup - here is the location prefix where Apache is to be installed later, - because Apache has to be configured for this location to work correctly. - But there are a lot of other options available for your pleasure.</p> - - <p>For a short impression of what possibilities you have, here is a - typical example which compiles Apache for the installation tree - /sw/pkg/apache with a particular compiler and flags plus the two - additional modules mod_rewrite and mod_proxy for later loading through - the DSO mechanism:</p> -<pre> - $ CC="pgcc" OPTIM="-O2" \ - ./configure --prefix=/usr/local/apache \ - --enable-module=rewrite --enable-shared=rewrite \ - --enable-module=proxy --enable-shared=proxy -</pre> - - <p>For a complete list of the available options, type the following - command:</p> - <p><code>./configure --help</code></p> - - <p>See also the file <code>README.configure</code> for listings of - example configurations.</p> - - <h3><a name="build">Building the package</a></h3> - - <p>Now you can build the various parts which form the Apache package by - simply running the command</p> -<pre> - $ make -</pre> - - <p>Please be patient here, this takes approximately 2 minutes to complete - under a Pentium-166/FreeBSD-2.2 system, dependent on the amount of - modules you have enabled.</p> - - <h3><a name="installing">Installing the package</a></h3> - - <p>Now its time to install the package under the configured installation - <code>PREFIX</code> (see the <code>--prefix</code> option above):</p> -<pre> - $ make install -</pre> - - <p>In the following examples, <code>PREFIX</code> is not the literal string - "PREFIX", but whatever argument you provided to - the<code>--prefix</code> option.</p> - -<!-- Building and installing Apache in the traditional way --> - - <h2><a name="traditional">Building and installing Apache in the traditional way</a></h2> - - Before the advent of APACI, there was just one way to build and - install Apache. While APACI gave a configuration interface which is - more familiar to some people, the older method gives a way to - configure the installation without typing a large number of - command-line options. - - <h3><a name="trad_configure">Configuring the installation</a></h3> - - Compiling Apache consists of three steps: First select which - Apache <strong>modules</strong> you want to include into the - server. Second create a configuration for your operating - system. Third compile the executable. - - <p>All configuration of Apache is performed in the - <code>src</code> directory of the Apache distribution. Change - into this directory.</p> - - <ol> - <li> - Select modules to compile into Apache in the <code>Configuration</code> - file <code>src/Configuration.tmpl</code>. Uncomment lines - corresponding to those optional modules you wish to include - (among the AddModule lines at the bottom of the file), or - add new lines corresponding to additional modules you have - downloaded or written. (See <a - href="misc/API.html">API.html</a> for preliminary docs on - how to write Apache modules). Advanced users can comment - out some of the default modules if they are sure they will - not need them (be careful though, since many of the default - modules are vital for the correct operation and security of - the server). - - <p>You should also read the instructions in the - <code>Configuration</code> file to see if you need to set - any of the <code>Rule</code> lines.</p> - </li> - - <li> - Configure Apache for your operating system. Normally you - can just run the <code>Configure</code> script as given - below. However if this fails or you have any special - requirements (<em>e.g.</em>, to include an additional - library required by an optional module) you might need to - edit one or more of the following options in the - <code>Configuration</code> file: <code>EXTRA_CFLAGS, LIBS, - LDFLAGS, INCLUDES</code>. - - <p>Run the <code>Configure</code> script:</p> - - <blockquote> -<pre> - % Configure - Using 'Configuration' as config file - + configured for <whatever> platform - + setting C compiler to <whatever> * - + setting C compiler optimization-level to <whatever> * - + Adding selected modules - + doing sanity check on compiler and options - Creating Makefile in support - Creating Makefile in main - Creating Makefile in os/unix - Creating Makefile in modules/standard - -</pre> - </blockquote> - (*: Depending on Configuration and your system, Configure - might not print these lines. That's OK). - - <p>This generates a Makefile for use in stage 3. It also - creates a Makefile in the support directory, for - compilation of the optional support programs.</p> - - <p>(If you want to maintain multiple configurations, you - can give an option to <code>Configure</code> to tell it to - read an alternative Configuration file, such as - <code>Configure -file Configuration.ai</code>).</p> - </li> - -<h3><a name="trad_compile">Compiling Apache</a></h3> - - <li>Type <code>make</code>.</li> - </ol> - The modules we place in the Apache distribution are the ones we - have tested and are used regularly by various members of the - Apache development group. Additional modules contributed by - members or third parties with specific needs or functions are - available at <<a - href="http://www.apache.org/dist/httpd/contrib/modules/">http://www.apache.org/dist/httpd/contrib/modules/</a>>. - There are instructions on that page for linking these modules - into the core Apache code. - - <h3><a name="trad_install">Installing Apache</a></h3> - You will have a binary file called <code>httpd</code> in the - <code>src</code> directory. A binary distribution of Apache - will supply this file. - - <p>The next step is to install the program and configure it. - Apache is designed to be configured and run from the same set - of directories where it is compiled. If you want to run it from - somewhere else, make a directory and copy the - <code>conf</code>, <code>logs</code> and <code>icons</code> - directories into it. In either case you should read the <a - href="misc/security_tips.html#serverroot">security tips</a> - describing how to set the permissions on the server root - directory.</p> - - <p>The next step is to edit the configuration files for the - server. This consists of setting up various - <strong>directives</strong> in up to three central - configuration files. By default, these files are located in the - <code>conf</code> directory and are called - <code>srm.conf</code>, <code>access.conf</code> and - <code>httpd.conf</code>. To help you get started there are same - files in the <code>conf</code> directory of the distribution, - called <code>srm.conf-dist</code>, - <code>access.conf-dist</code> and <code>httpd.conf-dist</code>. - Copy or rename these files to the names without the - <code>-dist</code>. Then edit each of the files. Read the - comments in each file carefully. Failure to setup these files - correctly could lead to your server not working or being - insecure. You should also have an additional file in the - <code>conf</code> directory called <code>mime.types</code>. - This file usually does not need editing.</p> - - <p>First edit <code>httpd.conf</code>. This sets up general - attributes about the server: the port number, the user it runs - as, <em>etc.</em> Next edit the <code>srm.conf</code> file; - this sets up the root of the document tree, special functions - like server-parsed HTML or internal imagemap parsing, - <em>etc.</em> Finally, edit the <code>access.conf</code> file - to at least set the base cases of access.</p> - - <p>In addition to these three files, the server behavior can be - configured on a directory-by-directory basis by using - <code>.htaccess</code> files in directories accessed by the - server.</p> - - <h3>Compiling Support Programs</h3> - In addition to the main <code>httpd</code> server which is - compiled and configured as above, Apache includes a number of - support programs. These are not compiled by default. The - support programs are in the <code>support</code> directory of - the distribution. To compile the support programs, change into - this directory and type -<pre> - make -</pre> - - <h2><a name="testing">Testing the package</a></h2> - - <p>Now you can fire up your Apache HTTP server by immediately running</p> -<pre> - $ PREFIX/bin/apachectl start -</pre> - - <p>and then you should be able to request your first document via URL - http://localhost/ (when you built and installed Apache as root or at - least used the --without-confadjust option) or http://localhost:8080/ - (when you built and installed Apache as a regular user). Then stop the - server again by running:</p> -<pre> - $ PREFIX/bin/apachectl stop -</pre> - - <h2><a name="time">Set your system time properly!</a></h2> - Proper operation of a public web server requires accurate time - keeping, since elements of the HTTP protocol are expressed as - the time of day. So, it's time to investigate setting up NTP or - some other time synchronization system on your Unix box, or - the <code>net time</code> command on NT. - - <hr /> - - <h3 align="CENTER">Apache HTTP Server</h3> - <a href="./"><img src="images/index.gif" alt="Index" /></a> - - </body> -</html> - - - diff --git a/usr.sbin/httpd/htdocs/manual/man-template.html b/usr.sbin/httpd/htdocs/manual/man-template.html deleted file mode 100644 index 463a48491f3..00000000000 --- a/usr.sbin/httpd/htdocs/manual/man-template.html +++ /dev/null @@ -1,111 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache module mod_foobar</title> - </head> - <!-- read and delete all blockquotes, and this comment --> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server</h3> - </div> - - - - <h1 align="CENTER">Module mod_foobar</h1> - - <blockquote> - <em>Add this file as a link in mod/index.html</em> - </blockquote> - - <p>This module is contained in the <code>mod_foobar.c</code> - file, and <strong>is/is not</strong> compiled in by default. It - provides for <strong>the foobar feature</strong>. Any document - with the mime type <samp>foo/bar</samp> will be processed by - this module.</p> - - <blockquote> - <em>Add the magic mime type to the list in - magic_types.html</em> - </blockquote> - - <h2>Summary</h2> - - <p><em>General module documentation here.</em></p> - - <h2>Directives</h2> - - <ul> - <li><a href="#adirective">ADirective</a></li> - </ul> - - <blockquote> - <em>Add these directives to the list in directives.html</em> - </blockquote> - <hr /> - <!-- the HR is part of the directive description --> - - <h2><a id="adirective" name="adirective">ADirective - directive</a></h2> - - <p><a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> ADirective <em>some - args</em><br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> <samp>ADirective - default value</samp><br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> context-list<br /> - </p> - - <blockquote> - <em>context-list is where this directive can appear; allowed: - server config, virtual host, directory, .htaccess</em> - </blockquote> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> override <br /> - - - <blockquote> - <em>required if the directive is allowed in .htaccess files; - the AllowOverride option that allows the directive.</em> - </blockquote> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> status <br /> - - - <blockquote> - <em>Core if in core apache, Base if in one of the standard - modules, Extension if in an extension module (not compiled in - by default) or Experimental</em> - </blockquote> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_foobar <br /> - <a href="directive-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> compatibility - notes - - <blockquote> - <em>Describe any compatibility issues, such as "Only - available in Apache 1.2 or later," or "The Apache syntax for - this directive is not compatible with the NCSA directive of - the same name."</em> - </blockquote> - - <p>The ADirective directive does something.</p> - <hr /> - - <h3 align="CENTER">Apache HTTP Server</h3> - <a href="./"><img src="images/index.gif" alt="Index" /></a> - - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/misc/HTTP_Features.tsv b/usr.sbin/httpd/htdocs/manual/misc/HTTP_Features.tsv deleted file mode 100644 index 893403d898f..00000000000 --- a/usr.sbin/httpd/htdocs/manual/misc/HTTP_Features.tsv +++ /dev/null @@ -1,142 +0,0 @@ -This tab-separated-value file is for use as a checklist -for features against <draft-ietf-http-v11-spec-rev-03.txt>, -since two independently developed and interoperable -implementations are needed for each feature. For each entry, - ? means not filled-in - - means not applicable - n means no - y means yes - Y means yes with the addition of a module that uses feature - -The contents should be placed in the form at <http://www.agranat.com:1998/> -by someone who wants to be the contact for the Apache Group. - -Section Feature Implemented Tested -8.1 Persistent Connections y y -8.2.3 Automatic retrying of requests - - -8.2.4 Use of the 100 (Continue) status n n -9.2 OPTIONS y y -9.3 GET y y -9.4 HEAD y y -9.5 POST y y -9.6 PUT Y y -9.7 DELETE Y y -9.8 TRACE y y -9.9 CONNECT y y -10.1.1 100 Continue y y -10.1.2 101 Switching Protocols Y n -10.2.1 200 OK y y -10.2.2 201 Created y y -10.2.3 202 Accepted y y -10.2.4 203 Non-Authoritative Information y y -10.2.5 204 No Content y y -10.2.6 205 Reset Content y y -10.2.7 206 Partial Content y y -10.3.1 300 Multiple Choices y y -10.3.2 301 Moved Permanently y y -10.3.3 302 Found y y -10.3.4 303 See Other y y -10.3.5 304 Not Modified y y -10.3.6 305 Use Proxy y n -10.3.7 307 Temporary Redirect n n -10.4.1 400 Bad Request y y -10.4.2 401 Unauthorized y y -10.4.3 402 Payment Required Y n -10.4.4 403 Forbidden y y -10.4.5 404 Not Found y y -10.4.6 405 Method Not Allowed y y -10.4.7 406 Not Acceptable y y -10.4.8 407 Proxy Authentication Required y y -10.4.9 408 Request Timeout y y -10.4.10 409 Conflict Y n -10.4.11 410 Gone y y -10.4.12 411 Length Required y y -10.4.13 412 Precondition Failed y y -10.4.14 413 Request Entity Too Large y y -10.4.15 414 Request-URI Too Long y y -10.4.16 415 Unsupported Media Type y n -10.4.17 416 Requested range not satisfiable n n -10.4.18 417 Expectation Failed n n -10.5.1 500 Internal Server Error y y -10.5.2 501 Not Implemented y y -10.5.3 502 Bad Gateway y y -10.5.4 503 Service Unavailable y y -10.5.5 504 Gateway Timeout y y -10.5.6 505 HTTP Version Not Supported Y n -13.3.3 Strong entity tags y y -13.3.3 Weak entity tags y y -14.1 Accept y y -14.2 Accept-Charset y y -14.3 Accept-Encoding n n -14.4 Accept-Language y y -14.5 Accept-Ranges y y -14.6 Age - - -14.7 Allow y y -14.8 Authorization y y -14.9 Cache-Control y y -14.10 Connection y y -14.11 Content-Encoding y y -14.12 Content-Language y y -14.13 Content-Length y y -14.14 Content-Location Y n -14.15 Content-MD5 y n -14.16 Content-Range y y -14.17 Content-Type y y -14.18 Date y y -14.19 ETag y y -14.20 Expect n n -14.21 Expires y y -14.22 From - - -14.23 Host y y -14.24 If-Modified-Since y y -14.25 If-Match y y -14.26 If-None-Match y y -14.27 If-Range y y -14.28 If-Unmodified-Since y y -14.29 Last-Modified y y -14.30 Location y y -14.31 Max-Forwards n n -14.32 Pragma y y -14.33 Proxy-Authenticate y y -14.34 Proxy-Authorization y y -14.35 Range y y -14.36 Referer y y -14.37 Retry-After y y -14.38 Server y y -14.39 TE n n -14.40 Trailer n n -14.41 Transfer-Encoding y y -14.42 Upgrade Y n -14.43 User-Agent - - -14.44 Vary y y -14.45 Via n n -14.46 Warning Y n -14.47 WWW-Authenticate y y -===== ===================================== -Same for <draft-ietf-http-authentication-01.txt>: - -A 2 Basic Authentication y y -A 3.2.1 WWW-Authenticate Digest y n -A 3.2.1 qop-options auth n n -A 3.2.1 qop-options auth-int n n -A 3.2.2 Authorization Digest y n -A 3.2.2 request qop auth n n -A 3.2.2 request qop auth-int n n -A 3.2.3 Authentication-Info Digest n n -A 3.2.3 response qop auth n n -A 3.2.3 response qop auth-int n n -A 4.1 Proxy-Authenticate Basic y y -A 4.2 Proxy-Authenticate Digest y n -A 4.2 Proxy qop-options auth n n -A 4.2 Proxy qop-options auth-int n n -A 4.2 Proxy Authorization Digest y n -A 4.2 Proxy request qop auth n n -A 4.2 Proxy request qop auth-int n n -A 4.2 Proxy Authentication-Info Digest n n -A 4.2 Proxy response qop auth n n -A 4.2 Proxy response qop auth-int n n - - -NOTES: -100 Continue sent on all bodied requests, as per RFC 2068. -Accept-Encoding does not allow q-values, as per RFC 2068. diff --git a/usr.sbin/httpd/htdocs/manual/misc/client_block_api.html b/usr.sbin/httpd/htdocs/manual/misc/client_block_api.html deleted file mode 100644 index 0b2f2faf6a4..00000000000 --- a/usr.sbin/httpd/htdocs/manual/misc/client_block_api.html +++ /dev/null @@ -1,97 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Reading Client Input in Apache 1.2</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">Reading Client Input in Apache 1.2</h1> - <hr /> - - <p>Apache 1.1 and earlier let modules handle POST and PUT - requests by themselves. The module would, on its own, determine - whether the request had an entity, how many bytes it was, and - then called a function (<code>read_client_block</code>) to get - the data.</p> - - <p>However, HTTP/1.1 requires several things of POST and PUT - request handlers that did not fit into this module, and all - existing modules have to be rewritten. The API calls for - handling this have been further abstracted, so that future HTTP - protocol changes can be accomplished while remaining - backwards-compatible.</p> - <hr /> - - <h3>The New API Functions</h3> -<pre> - int ap_setup_client_block (request_rec *, int read_policy); - int ap_should_client_block (request_rec *); - long ap_get_client_block (request_rec *, char *buffer, int buffer_size); -</pre> - - <ol> - <li> - Call <code>ap_setup_client_block()</code> near the - beginning of the request handler. This will set up all the - necessary properties, and will return either OK, or an - error code. If the latter, the module should return that - error code. The second parameter selects the policy to - apply if the request message indicates a body, and how a - chunked transfer-coding should be interpreted. Choose one - of -<pre> - REQUEST_NO_BODY Send 413 error if message has any body - REQUEST_CHUNKED_ERROR Send 411 error if body without Content-Length - REQUEST_CHUNKED_DECHUNK If chunked, remove the chunks for me. - REQUEST_CHUNKED_PASS Pass the chunks to me without removal. -</pre> - In order to use the last two options, the caller MUST - provide a buffer large enough to hold a chunk-size line, - including any extensions. - </li> - - <li>When you are ready to possibly accept input, call - <code>ap_should_client_block()</code>. This will tell the - module whether or not to read input. If it is 0, the module - should assume that the input is of a non-entity type - (<em>e.g.</em>, a GET request). A nonzero response indicates - that the module should proceed (to step 3). This step also - sends a 100 Continue response to HTTP/1.1 clients, so should - not be called until the module is - <strong>*definitely*</strong> ready to read content. - (otherwise, the point of the 100 response is defeated). Never - call this function more than once.</li> - - <li>Finally, call <code>ap_get_client_block</code> in a loop. - Pass it a buffer and its size. It will put data into the - buffer (not necessarily the full buffer, in the case of - chunked inputs), and return the length of the input block. - When it is done reading, it will return 0 if EOF, or -1 if - there was an error.</li> - </ol> - - <p>As an example, please look at the code in - <code>mod_cgi.c</code>. This is properly written to the new API - guidelines.</p> - <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/misc/compat_notes.html b/usr.sbin/httpd/htdocs/manual/misc/compat_notes.html deleted file mode 100644 index a2932f0987c..00000000000 --- a/usr.sbin/httpd/htdocs/manual/misc/compat_notes.html +++ /dev/null @@ -1,135 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache HTTP Server: Notes about Compatibility with - NCSA's Server</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">Compatibility Notes with NCSA's Server</h1> - <hr /> - While Apache is for the most part a drop-in replacement for - NCSA's httpd, there are a couple gotcha's to watch out for. - These are mostly due to the fact that the parser for config and - access control files was rewritten from scratch, so certain - liberties the earlier servers took may not be available here. - These are all easily fixable. If you know of other problems - that belong here, <a - href="http://httpd.apache.org/bug_report.html">let us know.</a> - - - <p>Please also check the <a - href="known_client_problems.html">known client problems</a> - page.</p> - - <ol> - <li>As of Apache 1.3.1, methods named in a <a - href="../mod/core.html#limit"><samp><Limit></samp></a> - section <em>must</em> be listed in upper-case. Lower- or - mixed-case method names will result in a configuration - error.</li> - - <li>The basic mod_auth <code>AuthGroupFile</code>-specified - group file format allows commas between user names - Apache - does not.</li> - - <li>If you follow the NCSA guidelines for setting up access - restrictions based on client domain, you may well have added - entries for <code>AuthType, AuthName, AuthUserFile</code> or - <code>AuthGroupFile</code>. <strong>None</strong> of these - are needed (or appropriate) for restricting access based on - client domain. When Apache sees <code>AuthType</code> it - (reasonably) assumes you are using some authorization type - based on username and password. Please remove - <code>AuthType</code>, it's unnecessary even for NCSA.</li> - - <li><code>OldScriptAlias</code> is no longer supported.</li> - - <li><code>exec cgi=""</code> produces reasonable - <strong>malformed header</strong> responses when used to - invoke non-CGI scripts.<br /> - The NCSA code ignores the missing header (bad idea).<br /> - Solution: write CGI to the CGI spec and use - <code>include virtual</code>, or use <code>exec - cmd=""</code> instead.</li> - - <li>Icons for FancyIndexing broken - well, no, they're not - broken, we've just upgraded the icons from flat .xbm files to - pretty and much smaller .gif files, courtesy of <a - href="mailto:kevinh@eit.com">Kevin Hughes</a> at <a - href="http://www.eit.com/">EIT</a>. If you are using the same - srm.conf from an old distribution, make sure you add the new - <a href="../mod/mod_autoindex.html#addicon">AddIcon</a>, <a - href="../mod/mod_autoindex.html#addiconbytype">AddIconByType</a>, - and <a - href="../mod/mod_autoindex.html#defaulticon">DefaultIcon</a> - directives.</li> - - <li>Apache versions before 1.2b1 will ignore the last line of - configuration files if the last line does not have a trailing - newline. This affects configuration files (httpd.conf, - access.conf and srm.conf), and htpasswd and htgroup - files.</li> - - <li>Apache does not permit commas delimiting the methods in - <Limit>.</li> - - <li>Apache's <code><VirtualHost></code> treats all - addresses as "optional" (<em>i.e.</em>, the server should - continue booting if it can't resolve the address). Whereas in - NCSA the default is to fail booting unless an added - <code>optional</code> keyword is included.</li> - - <li>Apache does not implement <code>OnDeny</code>; use <a - href="../mod/core.html#errordocument"><code>ErrorDocument</code></a> - instead.</li> - - <li>Apache (as of 1.3) always performs the equivalent of - <code>HostnameLookups minimal</code>. <code>minimal</code> is - not an option to <a - href="../mod/core.html#hostnamelookups"><code>HostnameLookups</code></a>.</li> - - <li>To embed spaces in directive arguments NCSA used a - backslash before the space. Apache treats backslashes as - normal characters. To embed spaces surround the argument with - double-quotes instead.</li> - - <li>Apache does not implement the NCSA <code>referer</code> - directive. See <a - href="http://bugs.apache.org/index/full/968">PR#968</a> for a - few brief suggestions on alternative ways to implement the - same thing under Apache.</li> - - <li>Apache does not allow ServerRoot settings inside a - VirtualHost container. There is only one global ServerRoot in - Apache; any desired changes in paths for virtual hosts need - to be made with the explicit directives, <em>e.g.</em>, - DocumentRoot, TransferLog, <em>etc.</em></li> - - <li>The <code>AddType</code> directive cannot be used to set - the type of particular files. Instead, you can scope you - directives using <Files> blocks.</li> - </ol> - More to come when we notice them.... - <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/misc/index.html b/usr.sbin/httpd/htdocs/manual/misc/index.html index 0663008bfb6..8415d4f4cc4 100644 --- a/usr.sbin/httpd/htdocs/manual/misc/index.html +++ b/usr.sbin/httpd/htdocs/manual/misc/index.html @@ -34,18 +34,6 @@ <dd>Frequently-Asked Questions concerning the Apache project and server.</dd> - <dt><a href="client_block_api.html">Reading Client Input in - Apache 1.2</a></dt> - - <dd>Describes differences between Apache 1.1 and 1.2 in how - modules read information from the client.</dd> - - <dt><a href="compat_notes.html">Compatibility with - NCSA</a></dt> - - <dd>Notes about Apache's compatibility with the NCSA - server.</dd> - <dt><a href="custom_errordocs.html">How to use XSSI and Negotiation for custom ErrorDocuments</a></dt> @@ -74,11 +62,6 @@ <dd>Instructions about how to accomplish some commonly-desired server functionality changes.</dd> - <dt><a href="HTTP_Features.tsv">HTTP Features list</a></dt> - - <dd>A tab-separate table of HTTP features implemented and - tested in Apache.</dd> - <dt><a href="known_client_problems.html">Known Client Problems</a></dt> @@ -109,12 +92,6 @@ <dd>Some "do"s - and "don't"s - for keeping your Apache web site secure.</dd> - <dt><a href="windoz_keepalive.html">Windows Bug with Web - Keepalive</a></dt> - - <dd>A brief description of a known problem with Microsoft - Windows and web sites accessed using keepalive - connections.</dd> </dl> <hr /> diff --git a/usr.sbin/httpd/htdocs/manual/misc/known_bugs.html b/usr.sbin/httpd/htdocs/manual/misc/known_bugs.html deleted file mode 100644 index 95bb37c705d..00000000000 --- a/usr.sbin/httpd/htdocs/manual/misc/known_bugs.html +++ /dev/null @@ -1,171 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> -<HTML> -<HEAD> -<TITLE>Apache HTTP Server Project</TITLE> -</HEAD> - -<!-- Background white, links blue (unvisited), navy (visited), red (active) --> -<BODY - BGCOLOR="#FFFFFF" - TEXT="#000000" - LINK="#0000FF" - VLINK="#000080" - ALINK="#FF0000" -> -<DIV ALIGN="CENTER"> - <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]"> - <H3> - Apache HTTP Server Version 1.2 - </H3> -</DIV> - -<H1 ALIGN="CENTER">Known Bugs in Apache</H1> - -The most up-to-date resource for bug tracking and information is the -<A HREF="http://www.apache.org/bugdb.cgi">Apache bug database</A>. -Significant bugs at release time will also be noted there. -If you are running a 1.2 beta release or version 1.1.3 or earlier -and thing you have found a bug, please upgrade to 1.2. Many bugs -in early versions have been fixed in 1.2. - -<P>See Also: <A HREF="compat_notes.html">Compatibility notes</A></P> -<HR> - -<H2>Apache 1.2 Bugs</H2> - -<OL> - <LI><b>Exists in 1.2.1 only.</b> - On Solaris 2.x the server will stop running after receiving a - SIGHUP. Four workarounds exist (choose one):<p> - <ul> - <li>Retrieve <a href="http://www.apache.org/dist/patches/apply_to_1.2.1/solaris_hup.patch">this patch</a>. - <code>cd</code> to your <code>apache_1.2.1</code> directory, and - type <code>patch -s -p1 < /path/to/patchfile</code>. Then rebuild - Apache.<p> - <li>Use SIGUSR1 instead of SIGHUP, see <a href="../stopping.html"> - Stopping and Restarting Apache</a> for more details.<p> - <li>Add <code>-DNO_SLACK</code> to - <code>EXTRA_CFLAGS</code> in - your <code>Configuration</code> file, re-run <code>Configure</code> - and rebuild your server. This disables the - <a href="descriptors.html">descriptor slack workaround</a><p> - <li>(Least preferable) Use Apache 1.2.0 instead of 1.2.1.<p> - </ul> - This problem will be tracked as - <a href="http://www.apache.org/bugdb.cgi/full/832">PR#832</a>.<p> - </li> - - <LI>(Exists in 1.2.0 and in 1.2.1 after either of the - <code>NO_SLACK</code> or patch provided by the previous bug are applied.) - Solaris 2.5.1 (and probably other versions of Solaris) appear to have - a race condition completely unrelated to all the others. It is possible - during a SIGHUP that the server will fail to start because it will not - be able to re-open its sockets. To our knowledge this has only shown - up during testing when we pummel the server with as many SIGHUP requests - per second as we can. This appears unrelated to the similar sounding bug - described in <a href="http://www.apache.org/bugdb.cgi/full/832">PR#832</a>. - <p> - - <LI><a name="listenbug">On some architectures</A> - if your configuration uses multiple - <a href="../mod/core.html#listen">Listen</a> directives then it is possible - that the server will starve one of the sockets while serving hits on - another. The work-around is to add - <code>-DUSE_FLOCK_SERIALIZED_ACCEPT</code> to the - <code>EXTRA_CFLAGS</code> line in your Configuration and rebuild. - (If you encounter problems with that, you can also try - <code>-DUSE_FCNTL_SERIALIZED_ACCEPT</code>.) - This affects any architecture that doesn't use one of the - <code>USE_xxxxx_SERIALIZED_ACCEPT</code> definitions, see the - source file <code>conf.h</code> for your architecture. - This will be tracked as - <a href="http://www.apache.org/bugdb.cgi/full/467">PR#467</a>. - <P></LI> - - <LI><b>Fixed in 1.2.1.</b> - <a name="cnegbug">Apache's</A> <A HREF="../content-negotiation.html">Content - Negotiation</A> should pick the smallest variant if there - are several that are equally acceptable. A bug in 1.2 means it no - longer does this unless all the variants have character sets. - This <A HREF="../../dist/contrib/patches/1.2/conneg-bug.patch">patch</A> - fixes this problem. It also fixes the problem which makes Apache - pick the last equally acceptable variant instead of the first. - This will be tracked as - <a href="http://www.apache.org/bugdb.cgi/full/94">PR#94</a>. - <P></LI> - - <LI> - The PATH_INFO part of a request URI cannot include the sequence - <CODE>%2f</CODE>. This will be tracked as - <A HREF="http://www.apache.org/bugdb.cgi/full/543">PR#543</A>. - <P></LI> - - <LI>Users of early 1.2 betas reported problems with many - connections stuck in the FIN_WAIT_2 state due to server - timeouts. Several changes were made during the beta testing of 1.2 - to reduce this problem as much as possible, although you may still - see sockets in FIN_WAIT_2 state due to network or operating system - issues outside the control of Apache. See our <A - HREF="fin_wait_2.html">FIN_WAIT_2</A> page for more details. - - <P>SunOS4 has a kernel bug in the allocation of memory for the mbuf table. - When it fills up, the result is a Panic the next time any routine tries - to set something in an imaginary mbuf beyond the range of the table. - Due to buggy browser behavior and the lack of a FIN_WAIT_2 timeout - on SunOS4, "KeepAlive Off" is necessary to avoid filling up the mbuf - table on busy sites. - <P></LI> - - <LI>Compilation fails on SCO3 when using gcc instead of cc, complaining - with "<CODE>gcc: noinline: No such file or directory</CODE>". Fix - is given in <a href="http://www.apache.org/bugdb.cgi/full/695">PR#695</A>. - <P></LI> - - <LI>If compilation fails complaining about "unknown symbol __inet_ntoa()" - then you have probably installed version 8 of bind. You will need to - explicitly link with the bind library by adding <CODE>-lbind</CODE> - to <CODE>EXTRA_LDFLAGS</CODE> in <CODE>Configuration</CODE>. See - <A HREF="http://www.apache.org/bugdb.cgi/full/616">PR#616</A> - and the - <A HREF="FAQ.html#bind8.1">Apache FAQ</A>. - <P></LI> - - <LI>The message "<CODE>created shared memory segment #730499</CODE>" - in error_log is not an error and should be ignored. See - <a href="http://www.apache.org/bugdb.cgi/full/696">PR#696</A>. - <P></LI> - - <LI> - Compiling on Solaris 2 with SunSoft's C compiler gives the warning - <CODE>"mod_include.c", line 1123: warning: end-of-loop code not - reached</CODE>. This is a bogus warning and can be ignored. - See <A HREF="http://www.apache.org/bugdb.cgi/full/681">PR#681</A>. - <P></LI> - - <LI><a href="descriptors.html"><b>Workaround available in 1.2.1.</b></a> - There appears to be a problem on BSDI 2.1 with large numbers of - virtual hosts. This appears similar to a file-descriptor limit - but BSDI should not have this problem. This will be tracked as - <A HREF="http://www.apache.org/bugdb.cgi/full/611">PR#611</A>. - See also the <A HREF="FAQ.html#fdlim">Apache FAQ</A>. - <P></LI> - - <LI><a href="descriptors.html"><b>Workaround available in 1.2.1.</b></a> - Solaris 2 has problems with large numbers of virtual hosts. This is - because of an operating system limit of 256 file pointers, not due - to Apache. See also the <A HREF="FAQ.html#fdlim">Apache FAQ</A>. - <P></LI> - -</OL> - -<HR> -<H3 ALIGN="CENTER"> - Apache HTTP Server Version 1.2 -</H3> - -<A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A> -<A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A> - -</BODY> -</HTML> - diff --git a/usr.sbin/httpd/htdocs/manual/misc/windoz_keepalive.html b/usr.sbin/httpd/htdocs/manual/misc/windoz_keepalive.html deleted file mode 100644 index ddb1935f09d..00000000000 --- a/usr.sbin/httpd/htdocs/manual/misc/windoz_keepalive.html +++ /dev/null @@ -1,64 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>MS Windows Netscape 3.0b4 KeepAlive problem - solved</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">HTTP/1.1 KeepAlive problems with Netscape - 3.0</h1> -<pre> -Date: Mon, 1 Jul 1996 16:03:06 -0700 (PDT) -From: Alexei Kosut <akosut@organic.com> -To: Apache Group -Subject: Re: keepalive and windoze - -Good news and good news (of a sort).. - -I was able to snag a Windows 95 machine here at Organic, and tried out -some things: - -1) On Netscape 3.0b4, I was able to reproduce the bug, each and every -time. It's really simple: go to the Network Setup panel. Set it to -"Connect Every Time" and only let it have 1 connection at once (this may -not be necessary, but it's helpful). Then load an image that's -kept-alive. Then wait until the connection times out (this depends on the -server - 10-30 seconds, except for MIIS, which never times out, near as I -can tell). Then hit reload. It will hang. (actually, once it crashed). - -2) This happens with all forms of server. Apache 1.1, Netscape 2.0, -Spyglass 1.2, NCSA 1.5 (although, as stated, I couldn't test MIIS). - -3) Netscape 3.0b5 does, indeed, *not* have this bug. At least, I couldn't -get it to perform such. Yipee. - -So, we just put up a note on the web page. Make sure we say that all the -servers have the bug, it's a Windows bug, and Netscape Navigator 3.0b5 -works around it. That way, no one can yell at us. Yes? - --- Alexei Kosut <akosut@organic.com> The Apache HTTP Server - http://www.nueva.pvt.k12.ca.us/~akosut/ http://www.apache.org/ -</pre> - <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/mod/core.html.html b/usr.sbin/httpd/htdocs/manual/mod/core.html.html index 6d90427d685..dcfd27616f6 100644 --- a/usr.sbin/httpd/htdocs/manual/mod/core.html.html +++ b/usr.sbin/httpd/htdocs/manual/mod/core.html.html @@ -2308,9 +2308,6 @@ Syntax OK Issues</a><br /> <strong>See Also:</strong> <a href="../bind.html">Setting which addresses and ports Apache uses</a><br /> - <strong>See Also:</strong> <a - href="http://httpd.apache.org/info/known_bugs.html#listenbug">Known - Bugs</a></p> <hr /> <h2><a id="listenbacklog" name="listenbacklog">ListenBacklog diff --git a/usr.sbin/httpd/htdocs/manual/mod/directives.html.html b/usr.sbin/httpd/htdocs/manual/mod/directives.html.html index c2b7d78ba6d..8437b26c22a 100644 --- a/usr.sbin/httpd/htdocs/manual/mod/directives.html.html +++ b/usr.sbin/httpd/htdocs/manual/mod/directives.html.html @@ -255,8 +255,6 @@ <li><a href="core.html#errorlog">ErrorLog</a></li> - <li><a href="mod_example.html#example">Example</a></li> - <li><a href="mod_expires.html#expiresactive">ExpiresActive</a></li> @@ -314,18 +312,6 @@ <li><a href="mod_autoindex.html#indexorderdefault">IndexOrderDefault</a></li> - <li><a - href="mod_isapi.html#isapireadaheadbuffer">ISAPIReadAheadBuffer</a></li> - - <li><a - href="mod_isapi.html#isapilognotsupported">ISAPILogNotSupported</a></li> - - <li><a - href="mod_isapi.html#isapiappendlogtoerrors">ISAPIAppendLogToErrors</a></li> - - <li><a - href="mod_isapi.html#isapiappendlogtoquery">ISAPIAppendLogToQuery</a></li> - <li><a href="core.html#keepalive">KeepAlive</a></li> <li><a diff --git a/usr.sbin/httpd/htdocs/manual/mod/index-bytype.html.html b/usr.sbin/httpd/htdocs/manual/mod/index-bytype.html.html index 215017c4b01..551f821e4b1 100644 --- a/usr.sbin/httpd/htdocs/manual/mod/index-bytype.html.html +++ b/usr.sbin/httpd/htdocs/manual/mod/index-bytype.html.html @@ -191,9 +191,6 @@ <dd>Executing CGI scripts based on media type or request method</dd> - <dt><a href="mod_isapi.html">mod_isapi</a> WIN32 only</dt> - - <dd>Windows ISAPI Extension support</dd> </dl> <h2>Internal Content Handlers</h2> @@ -258,15 +255,6 @@ improve performace</dd> </dl> - <h2>Development</h2> - - <dl> - <dt><a href="mod_example.html">mod_example</a> Apache 1.2 and - up</dt> - - <dd>Demonstrates Apache API</dd> - </dl> - <h2>Obsolete</h2> <dl> @@ -282,12 +270,6 @@ <dd>Support for Netscape-like cookies. Replaced in Apache 1.2 by mod_usertrack</dd> - <dt><a href="mod_dld.html">mod_dld</a> Apache 1.2.* and - earlier</dt> - - <dd>Start-time linking with the GNU libdld. Replaced in - Apache 1.3 by mod_so</dd> - <dt><a href="mod_log_common.html">mod_log_common</a> up to Apache 1.1.1</dt> diff --git a/usr.sbin/httpd/htdocs/manual/mod/index.html.html b/usr.sbin/httpd/htdocs/manual/mod/index.html.html index c9d5ffe2f56..864795cf31b 100644 --- a/usr.sbin/httpd/htdocs/manual/mod/index.html.html +++ b/usr.sbin/httpd/htdocs/manual/mod/index.html.html @@ -112,21 +112,10 @@ <dd>Basic directory handling</dd> - <dt><a href="mod_dld.html">mod_dld</a> Apache 1.2.* and - earlier</dt> - - <dd>Start-time linking with the GNU libdld. Replaced in - Apache 1.3 by mod_so</dd> - <dt><a href="mod_env.html">mod_env</a> Apache 1.1 and up</dt> <dd>Passing of environments to CGI scripts</dd> - <dt><a href="mod_example.html">mod_example</a> Apache 1.2 and - up</dt> - - <dd>Demonstrates Apache API</dd> - <dt><a href="mod_expires.html">mod_expires</a> Apache 1.2 and up</dt> @@ -151,10 +140,6 @@ <dd>Server configuration information</dd> - <dt><a href="mod_isapi.html">mod_isapi</a> WIN32 only</dt> - - <dd>Windows ISAPI Extension support</dd> - <dt><a href="mod_log_agent.html">mod_log_agent</a></dt> <dd>Logging of User Agents</dd> diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_dld.html b/usr.sbin/httpd/htdocs/manual/mod/mod_dld.html deleted file mode 100644 index fef211b7fd8..00000000000 --- a/usr.sbin/httpd/htdocs/manual/mod/mod_dld.html +++ /dev/null @@ -1,110 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache module mod_dld</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">Module mod_dld</h1> - <strong><font color="red">This module is obsolete. As of - version 1.3 of Apache, it has been replaced with <a - href="mod_so.html">mod_so</a>.</font></strong> This module is - contained in the <code>mod_dld.c</code> file, and is not - compiled in by default. It provides for loading of executable - code and modules into the server at start-up time, using the - GNU dld library. - - <h2>Summary</h2> - The optional dld module is a proof-of-concept piece of code - which loads other modules into the server as it is configuring - itself (the first time only; for now, rereading the config - files cannot affect the state of loaded modules), using the GNU - dynamic linking library, DLD. It isn't compiled into the server - by default, since not everyone has DLD, but it works when I try - it. (Famous last words.) - - <p>Note that for some reason, <code>LoadFile /lib/libc.a</code> - seems to be required for just about everything.</p> - - <p>Note: that DLD needs to read the symbol table out of the - server binary when starting up; these commands will fail if the - server can't find its own binary when it starts up, or if that - binary is stripped.</p> - - <h2>Directives</h2> - - <ul> - <li><a href="#loadfile">LoadFile</a></li> - - <li><a href="#loadmodule">LoadModule</a></li> - </ul> - <hr /> - - <h2><a id="loadfile" name="loadfile">LoadFile</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> LoadFile <em>filename - filename ...</em><br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Experimental<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_dld - - <p>The LoadFile directive links in the named object files or - libraries when the server is started; this is used to load - additional code which may be required for some module to work. - <em>Filename</em> is relative to <a - href="core.html#serverroot">ServerRoot</a>.</p> - <hr /> - - <h2><a id="loadmodule" name="loadmodule">LoadModule</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> LoadModule <em>module - filename</em><br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Experimental<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_dld - - <p>The LoadModule directive links in the object file or library - <em>filename</em> and adds the module structure named - <em>module</em> to the list of active modules. <em>Module</em> - is the name of the external variable of type - <code>module</code> in the file. Example:</p> - - <blockquote> - <code>LoadModule ai_backcompat_module - modules/mod_ai_backcompat.o<br /> - LoadFile /lib/libc.a</code> - </blockquote> - loads the module in the modules subdirectory of the ServerRoot. - - - <p> <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </p> - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_example.html b/usr.sbin/httpd/htdocs/manual/mod/mod_example.html deleted file mode 100644 index cbe5a6d8368..00000000000 --- a/usr.sbin/httpd/htdocs/manual/mod/mod_example.html +++ /dev/null @@ -1,165 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache module mod_example</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">Module mod_example</h1> - - <p>This module illustrates many of the aspects of the <a - href="../misc/API.html" rel="Help">Apache 1.2 API</a> and, when - used, demonstrates the manner in which module callbacks are - triggered by the server.</p> - - <p><a href="module-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Extension<br /> - <a href="module-dict.html#SourceFile" - rel="Help"><strong>Source File:</strong></a> - mod_example.c<br /> - <a href="module-dict.html#ModuleIdentifier" - rel="Help"><strong>Module Identifier:</strong></a> - example_module<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> Available in - Apache 1.2 and later.</p> - - <h2>Summary</h2> - - <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: -<pre> - AddModule modules/example/mod_example.o - -</pre> - </li> - - <li>Run the <code>src/Configure</code> script - ("<samp>cd src; ./Configure</samp>"). 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 "<samp>make</samp>" in the - <code>src</code> directory).</li> - </ol> - - <p>To add another module of your own:</p> - - <ol type="A"> - <li><samp>mkdir src/modules/<em>mymodule</em></samp></li> - - <li><samp>cp src/modules/example/* - src/modules/<em>mymodule</em></samp></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 <samp>mod_example</samp> Module</h2> - - <p>To activate the example module, include a block similar to - the following in your <samp>srm.conf</samp> file:</p> -<pre> - <Location /example-info> - SetHandler example-handler - </Location> - -</pre> - - <p>As an alternative, you can put the following into a <a - href="core.html#accessfilename"><samp>.htaccess</samp></a> file - and then request the file "test.example" from that - location:</p> -<pre> - AddHandler example-handler .example - -</pre> - - <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 id="example" name="example">Example directive</a></h2> - - <p><a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> Example<br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> None<br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config, virtual - host, directory, .htaccess<br /> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> Options<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Extension<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_example<br /> - <a href="directive-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> - <samp>Example</samp> is only available in Apache 1.2 and - later.</p> - - <p>The <samp>Example</samp> 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 "<samp>Example - directive declared here: YES/NO</samp>".</p> - <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/mod/mod_isapi.html b/usr.sbin/httpd/htdocs/manual/mod/mod_isapi.html deleted file mode 100644 index 4a6d458165a..00000000000 --- a/usr.sbin/httpd/htdocs/manual/mod/mod_isapi.html +++ /dev/null @@ -1,345 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache module mod_isapi</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="../images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server Version 1.3</h3> - </div> - - - <h1 align="CENTER">Module mod_isapi</h1> - - <p>This module supports ISAPI Extensions within Apache for - Windows.</p> - - <p><a href="module-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Base<br /> - <a href="module-dict.html#SourceFile" - rel="Help"><strong>Source File:</strong></a> mod_isapi.c<br /> - <a href="module-dict.html#ModuleIdentifier" - rel="Help"><strong>Module Identifier:</strong></a> - isapi_module<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> WIN32 only</p> - - <h2>Summary</h2> - - <p>This module implements the Internet Server extension API. It - allows Internet Server extensions (<em>e.g.</em> ISAPI .dll - modules) to be served by Apache for Windows, subject to the - noted restrictions.</p> - - <p>ISAPI extension modules (.dll files) are written by third - parties. The Apache Group does not author these modules, so we - provide no support for them. Please contact the ISAPI's author - directly if you are experiencing problems running their ISAPI - extention. <strong>Please <em>do not</em> post such problems to - Apache's lists or bug reporting pages.</strong></p> - - <h2>Directives</h2> - - <ul> - <li><a - href="#isapireadaheadbuffer">ISAPIReadAheadBuffer</a></li> - - <li><a - href="#isapilognotsupported">ISAPILogNotSupported</a></li> - - <li><a - href="#isapiappendlogtoerrors">ISAPIAppendLogToErrors</a></li> - - <li><a - href="#isapiappendlogtoquery">ISAPIAppendLogToQuery</a></li> - </ul> - - <h2>Usage</h2> - - <p>In the server configuration file, use the AddHandler - directive to associate ISAPI files with the - <code>isapi-isa</code> handler, and map it to the with their - file extensions. To enable any .dll file to be processed as an - ISAPI extention, edit the httpd.conf file and add the following - line:</p> -<pre> - AddHandler isapi-isa .dll -</pre> - - <p>ISAPI extensions are governed by the same permissions and - restrictions as CGI scripts. That is, <code>Options - ExecCGI</code> must be set for the directory that contains the - ISAPI .dll file.</p> - - <p>Review the <a href="#notes">Additional Notes</a> and the <a - href="#journal">Programmer's Journal</a> for additional details - and clarification of the specific ISAPI support offered by - mod_isapi.</p> - - <h2><a id="notes" name="notes">Additional Notes</a></h2> - - <p>Apache's ISAPI implementation conforms to all of the ISAPI - 2.0 specification, except for the "Microsoft-specific" - extensions dealing with asynchronous I/O. Apache's I/O model - does not allow asynchronous reading and writing in a manner - that the ISAPI could access. If an ISA tries to access - unsupported features, including async I/O, a message is placed - in the error log to help with debugging. Since these messages - can become a flood, a new directive; <code>ISAPILogNotSupported - Off</code>, is introduced in Apache 1.3.13.</p> - - <p>Some servers, like Microsoft IIS, load the ISA into the - server, and keep it loaded until memory usage is too high, or - specific configuration options are used. Apache currently loads - and unloads the ISA for each request. This is inefficient, but - Apache's request model makes this method the only method that - currently works. Apache 2.0 is expected to support more - effective loading and caching methods, with more precise - control over individual ISAPI modules and directories.</p> - - <p>Also, remember that while Apache supports ISAPI Extensions, - it <strong>does not support ISAPI Filters.</strong> Support for - filters may be added at a later date, but no support is planned - at this time.</p> - - <h2><a id="journal" name="journal">Programmer's - Journal</a></h2> - - <p>If you are programming Apache 1.3 mod_isapi modules, you - must limit your calls to ServerSupportFunction to the following - directives:</p> - - <dl> - <dt>HSE_REQ_SEND_URL_REDIRECT_RESP</dt> - - <dd>Redirect the user to another location.<br /> - This must be a fully qualified URL (e.g. - http://server/location).</dd> - - <dt>HSE_REQ_SEND_URL</dt> - - <dd>Redirect the user to another location.<br /> - This cannot be a fully qualified URL, you are not allowed to - pass the protocol or a server name (e.g. simply - /location).<br /> - This redirection is handled by the server, not the - browser.<br /> - <strong>Warning:</strong> in their recent documentation, - Microsoft appears to have abandoned the distinction between - the two HSE_REQ_SEND_URL functions. Apache continues to treat - them as two distinct functions with different requirements - and behaviors.</dd> - - <dt>HSE_REQ_SEND_RESPONSE_HEADER</dt> - - <dd>Apache accepts a response body following the header if it - follows the blank line (two consecutive newlines) in the - headers string argument. This body cannot contain NULLs, - since the headers argument is NULL terminated.</dd> - - <dt>HSE_REQ_DONE_WITH_SESSION</dt> - - <dd>Apache considers this a no-op, since the session will be - finished when the ISAPI returns from processing.</dd> - - <dt>HSE_REQ_MAP_URL_TO_PATH</dt> - - <dd>Apache will translate a virtual name to a physical - name.</dd> - - <dt>HSE_APPEND_LOG_PARAMETER <em>Apache 1.3.13 and - later</em></dt> - - <dd> - This logged message may be captured in any of the following - logs: - - <ul> - <li>in the \"%{isapi-parameter}n\" component in a - CustomLog directive</li> - - <li>in the %q log component with the - ISAPIAppendLogToQuery On directive</li> - - <li>in the error log with the ISAPIAppendLogToErrors On - directive</li> - </ul> - The first option, the %{isapi-parameter}n component, is - always available and prefered. - </dd> - - <dt>HSE_REQ_IS_KEEP_CONN <em>Apache 1.3.13 and - later</em></dt> - - <dd>Will return the negotiated Keep-Alive status.</dd> - - <dt>HSE_REQ_SEND_RESPONSE_HEADER_EX <em>Apache 1.3.13 and - later</em></dt> - - <dd>Will behave as documented, although the fKeepConn flag is - ignored.</dd> - - <dt>HSE_REQ_IS_CONNECTED <em>Apache 1.3.13 and - later</em></dt> - - <dd>Will report false if the request has been aborted.</dd> - </dl> - - <p>Apache returns FALSE to any unsupported call to - ServerSupportFunction, and sets the GetLastError value to - ERROR_INVALID_PARAMETER.</p> - - <p>Prior to Apache 1.3.13, ReadClient was a noop, and any - request with a request body greater than 48kb was rejected by - mod_isapi. As of Apache 1.3.13, ReadClient now retrieves the - request body exceeding the initial buffer (defined by - ISAPIReadAheadBuffer). Based on the ISAPIReadAheadBuffer - setting (number of bytes to buffer prior to calling the ISAPI - handler) shorter requests are sent complete to the extension - when it is invoked. If the request is longer, the ISAPI - extension must use ReadClient to retrieve the remaining request - body.</p> - - <p>WriteClient is supported, but only with the HSE_IO_SYNC flag - or no option flag (value of 0). Any other WriteClient request - will be rejected with a return value of FALSE, and a - GetLastError value of ERROR_INVALID_PARAMETER.</p> - - <p>GetServerVariable is supported, although extended server - variables do not exist (as defined by other servers.) All the - usual Apache CGI environment variables are available from - GetServerVariable. As of Apache 1.3.13, the ALL_HTTP and - ALL_RAW and variables are now available.</p> - - <p>Apache 2.0 mod_isapi may support additional features - introduced in later versions of the ISAPI specification, as - well as limited emulation of async I/O and the TransmitFile - semantics. Apache 2.0 may also support caching of ISAPI .dlls - for performance. No further enhancements to the Apache 1.3 - mod_isapi features are anticipated.</p> - <hr /> - - <h2><a id="isapireadaheadbuffer" - name="isapireadaheadbuffer">ISAPIReadAheadBuffer - directive</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> ISAPIReadAheadBuffer - <em>size</em><br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> 49152<br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> None<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Base<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_isapi<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> Apache 1.3.13 - and later, Win32 only - - <p>Defines the maximum size of the Read Ahead Buffer sent to - ISAPI extentions when they are initally invoked. All remaining - data must be retrieved using the ReadClient callback; some - ISAPI extensions may not support the ReadClient function. Refer - questions to the ISAPI extention's author.</p> - <hr /> - - <h2><a id="isapilognotsupported" - name="isapilognotsupported">ISAPILogNotSupported - directive</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> ISAPILogNotSupported - on|off<br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> on<br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> None<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Base<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_isapi<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> Apache 1.3.13 - and later, Win32 only - - <p>Logs all requests for unsupported features from ISAPI - extentions in the server error log. While this should be turned - off once all desired ISAPI modules are functioning, it defaults - to on to help administrators track down problems.</p> - <hr /> - - <h2><a id="isapiappendlogtoerrors" - name="isapiappendlogtoerrors">ISAPIAppendLogToErrors - directive</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> ISAPIAppendLogToErrors - on|off<br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> off<br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> None<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Base<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_isapi<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> Apache 1.3.13 - and later, Win32 only - - <p>Record HSE_APPEND_LOG_PARAMETER requests from ISAPI - extentions to the server error log.</p> - <hr /> - - <h2><a id="isapiappendlogtoquery" - name="isapiappendlogtoquery">ISAPIAppendLogToQuery - directive</a></h2> - - <a href="directive-dict.html#Syntax" - rel="Help"><strong>Syntax:</strong></a> ISAPIAppendLogToQuery - on|off<br /> - <a href="directive-dict.html#Default" - rel="Help"><strong>Default:</strong></a> off<br /> - <a href="directive-dict.html#Context" - rel="Help"><strong>Context:</strong></a> server config<br /> - <a href="directive-dict.html#Override" - rel="Help"><strong>Override:</strong></a> None<br /> - <a href="directive-dict.html#Status" - rel="Help"><strong>Status:</strong></a> Base<br /> - <a href="directive-dict.html#Module" - rel="Help"><strong>Module:</strong></a> mod_isapi<br /> - <a href="module-dict.html#Compatibility" - rel="Help"><strong>Compatibility:</strong></a> Apache 1.3.13 - and later, Win32 only - - <p>Record HSE_APPEND_LOG_PARAMETER requests from ISAPI - extentions to the query field (appended to the CustomLog %q - component).</p> - - <p> <hr /> - - <h3 align="CENTER">Apache HTTP Server Version 1.3</h3> - <a href="./"><img src="../images/index.gif" alt="Index" /></a> - <a href="../"><img src="../images/home.gif" alt="Home" /></a> - - </p> - </body> -</html> - diff --git a/usr.sbin/httpd/htdocs/manual/sitemap.html b/usr.sbin/httpd/htdocs/manual/sitemap.html index 16a4e131a06..998bf04747e 100644 --- a/usr.sbin/httpd/htdocs/manual/sitemap.html +++ b/usr.sbin/httpd/htdocs/manual/sitemap.html @@ -26,7 +26,6 @@ <li>Using the Apache HTTP Server <ul> -<li><a href="install.html">Compiling and Installing Apache</a></li> <li><a href="invoking.html">Starting Apache</a></li> <li><a href="stopping.html">Stopping and Restarting Apache</a></li> <li><a href="configuring.html">Configuration Files</a></li> @@ -112,13 +111,11 @@ Side Includes</a></li> <li><a href="mod/mod_digest.html">Apache module mod_digest</a></li> <li><a href="mod/mod_dir.html">Apache module mod_dir</a></li> <li><a href="mod/mod_env.html">Apache module mod_env</a></li> -<li><a href="mod/mod_example.html">Apache module mod_example</a></li> <li><a href="mod/mod_expires.html">Apache module mod_expires</a></li> <li><a href="mod/mod_headers.html">Apache module mod_headers</a></li> <li><a href="mod/mod_imap.html">Apache module mod_imap</a></li> <li><a href="mod/mod_include.html">Apache module mod_include</a></li> <li><a href="mod/mod_info.html">Apache module mod_info</a></li> -<li><a href="mod/mod_isapi.html">Apache module mod_isapi</a></li> <li><a href="mod/mod_log_agent.html">Apache module mod_log_agent</a></li> <li><a href="mod/mod_log_config.html">Apache module mod_log_config</a></li> <li><a href="mod/mod_log_referer.html">Apache module mod_log_referer</a></li> @@ -146,13 +143,10 @@ Side Includes</a></li> <li><a href="multilogs.html">Apache Multiple Log Files</a></li> <li><a href="process-model.html">Server Pool Management</a></li> <li><a href="sourcereorg.html">Source Re-organisation</a></li> -<li><a href="misc/compat_notes.html">Notes about Compatibility with NCSA's Server</a></li> <li><a href="misc/custom_errordocs.html">International Customized Server Error Messages</a></li> <li><a href="misc/descriptors.html">Descriptors and Apache</a></li> <li><a href="misc/fin_wait_2.html">Connections in FIN_WAIT_2 and Apache</a></li> <li><a href="misc/known_client_problems.html">Known Client Problems</a></li> -<li><a href="misc/windoz_keepalive.html">MS Windows Netscape 3.0b4 KeepAlive problem solved</a></li> -<li><a href="misc/client_block_api.html">Reading Client Input in Apache 1.2</a></li> </ul></li> </ul></li> diff --git a/usr.sbin/httpd/htdocs/manual/sourcereorg.html b/usr.sbin/httpd/htdocs/manual/sourcereorg.html deleted file mode 100644 index f1d7cbf6f0b..00000000000 --- a/usr.sbin/httpd/htdocs/manual/sourcereorg.html +++ /dev/null @@ -1,297 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Source Re-organisation</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <div align="CENTER"> - <img src="images/sub.gif" alt="[APACHE DOCUMENTATION]" /> - - <h3>Apache HTTP Server</h3> - </div> - - - - <h1 align="CENTER">Source Re-organisation</h1> - As of 1.3, the Apache source directories have been - re-organised. This re-organisation is designed to simplify the - directory structure, make it easier to add additional modules, - and to give module authors a way of specifying compile time - options or distribute binary modules. - - <h2>Summary of Changes</h2> - The source changes are: - - <ul> - <li>The non-module source files have moved from - <code>src</code> into <code>src/main</code></li> - - <li>The module source files previously in <code>src</code> - have moved to <code>src/modules/standard</code></li> - - <li>The <code>support</code> directory is now in - <code>src/support</code></li> - - <li>The existing symbol names used for global Apache function - and variable identifiers have been renamed in the source. - This way namespace conflicts are avoided when linking Apache - with third-party libraries. See the file - <code>src/include/compat.h</code> both for the list of - renamed symbol names and for a way to get source backward - compatibility in existing third-party module sources.</li> - </ul> - In addition, the following enhancements have been made: - - <ul> - <li>OS abstractions can be added in the <code>src/os</code> - directory. Currently this contains information for unix, OS/2 - and Windows 32 platforms.</li> - - <li><code>Configuration</code> syntax has been simplified for - adding new modules. Users no longer need to enter the - module's structure name. In addition, new modules can be - located anywhere on the file system, or typically in new or - existing directories under <code>src/modules</code>.</li> - - <li>Module authors can give simpler instructions for adding - their modules to Apache compilation. They can also now - provide compile time information required by - <code>Configure</code>, such as additional libraries - required.</li> - - <li>Module authors can distribute pre-compiled (.a or .o) - versions of their modules if required, along with a "module - definition file" which contains the information required by - <code>Configure</code>.</li> - - <li>All the sub-directories (main, modules/* and os/*) are - built as libraries.</li> - - <li>The new Apache Autoconf-style Interface (APACI) script - named <code>configure</code> replaced the old top-level - <code>Makefile</code> and - <code>src/helpers/InstallApache</code> stuff.</li> - </ul> - - <h2>Adding Modules</h2> - Modules are added to Apache by adding a reference to them in - <code>src/Configuration</code> then running - <code>Configure</code> and <code>make</code>. In earlier - version of Apache before 1.3, the line added to Configuration - looked like this: -<pre> - Module status_module mod_status.o -</pre> - From 1.3 onwards, the <code>AddModule</code> line should be - used instead, and typically looks like this: -<pre> - AddModule modules/standard/mod_status.o -</pre> - The argument to AddModule is the path, relative to - <code>src</code>, to the module file's source or object file. - - <p>Normally when adding a module you should follow the - instructions of the module author. However if the module comes - as a single source file, say mod_foo.c, then the recommended - way to add the module to Apache is as follows:</p> - - <ul> - <li>Put <code>mod_foo.c</code> into the directory - <code>src/modules/extra</code></li> - - <li>Go to the <code>src</code> directory and add the - following line to <code>Configuration</code><br /> - <code>AddModule modules/extra/mod_foo.o</code></li> - - <li>Run <code>./Configure</code></li> - - <li>Run <code>make</code></li> - </ul> - - <h2>New Facilities for Module Authors</h2> - In previous releases of Apache, new modules were added to the - <code>src</code> directory, and if the module required any - additional compilation options (such as libraries) they would - have to be added to <code>Configuration</code>. Also the user - would have to be told the module's structure name to add on the - Module line of <code>Configuration</code>. - - <p>From Apache 1.3 onwards, module authors can make use of - these new features:</p> - - <ul> - <li>Simplified <code>Configuration</code> command AddModule - which only requires a path to the module source or object - file</li> - - <li>If the module requires compile time options (such as - extra libraries) these can be specified in the module file - source or an external "module definition file".</li> - - <li>If a module is distributed as binary (.o or .a) then an - external "module definition file" can also be distributed - which gives the information Configure needs to add the - module, such as extra libraries and the module's structure - name.</li> - - <li>Modules can be installed anywhere on the file system, - although a directory under <code>src/modules</code> is - recommended.</li> - - <li>If the module is in its own directory, Apache can - automatically create a Makefile to build the module given a - file containing the module's dependencies.</li> - - <li>For building a third-party module - <strong>outside</strong> the Apache source tree the new - <code>apxs</code> support tool can be used to compile the - module into a <a href="dso.html">dynamic shared object - (DSO)</a>, install it into the existing Apache installation - and optionally activating it in the Apache - <code>httpd.conf</code> file. The only requirement is that - Apache has DSO-support for the used platform and the module - <code><a href="mod/mod_so.html">mod_so</a></code> was built - into the server binary <code>httpd</code>.</li> - </ul> - The rest of this document shows how to package modules for - Apache 1.3 and later and what to tell end-users of the module. - - <h3>Building a simple source distribution</h3> - Consider a simple add-on module, distributed as a single file. - For example, say it is called mod_demo.c. The archive for this - module should consist of two files, in a suitable directory - name. For example: - - <ul> - <li>mod_demo/mod_demo.c</li> - - <li>mod_demo/Makefile.tmpl</li> - </ul> - (Of course end-user instructions, README's, etc can also be - supplied in the archive). The end user should be told to - extract this archive in the <code>src/modules</code> directory - of their Apache source tree. This will create a new directory - <code>src/modules/mod_demo</code>. Then they need to add the - following line to the <code>Configuration</code> file: -<pre> - AddModule modules/mod_demo/mod_demo.o -</pre> - then run <code>Configure</code> and <code>make</code> as - normal. - - <p>The <code>mod_demo/Makefile.tmpl</code> should contain the - dependencies of the module source. For example, a simple module - which just interfaces to some standard Apache module API - functions might look this this:</p> -<pre> - mod_demo.o: mod_demo.c $(INCDIR)/httpd.h $(INCDIR)/http_protocol.h -</pre> - When the user runs <code>Configure</code> Apache will create a - full makefile to build this module. If this module also - requires some additional built-time options to be given, such - as libraries, see the next section. - - <p>If the module also comes with header files, these can be - added to the archive. If the module consists of multiple source - files it can be built into a library file using a supplied - makefile. In this case, distribute the makefile as - <code>mod_demo/Makefile</code> and <strong>do not</strong> - include a <code>mod_demo/Makefile.tmpl</code>. If - <code>Configure</code> sees a <code>Makefile.tmpl</code> it - assumes it is safe to overwrite any existing - <code>Makefile</code>.</p> - - <p>See the Apache <code>src/modules/standard</code> for an - example of a module directory where the makefile is created - automatically from a Makefile.tmpl file (note that this - directory also shows how to distribute multiple modules in a - single directory). See <code>src/modules/proxy</code> and - <code>src/modules/example</code> for examples of modules built - using custom makefiles (to build a library and an object file, - respectively).</p> - - <h3>Adding Compile time Information</h3> - Apache source files (or module definition files, see below) can - contain information used by <code>Configure</code> to add - compile-time options such as additional libraries. For example, - if mod_demo in the example above also requires that Apache be - linked against a DBM library, then the following text could be - inserted into the mod_demo.c source: -<pre> -/* - * Module definition information - the part between the -START and -END - * lines below is used by Configure. This could be stored in a separate - * instead. - * - * MODULE-DEFINITION-START - * Name: demo_module - * ConfigStart - LIBS="$LIBS $DBM_LIB" - if [ "X$DBM_LIB" != "X" ]; then - echo " + using $DBM_LIB for mod_demo" - fi - * ConfigEnd - * MODULE-DEFINITION-END - */ -</pre> - Note that this is contained inside a C language comment to hide - it from the compiler. Anything between the lines which contains - <code>MODULE-DEFINITION-START</code> and - <code>MODULE-DEFINITION-END</code> is used by - <code>Configure</code>. The <code>Name:</code> line gives the - module's structure name. This is not really necessary in this - case since if not present <code>Configure</code> will guess at - a name based on the filename (<em>e.g.</em>, given "mod_demo" - it will remove the leading "mod_" and append "_module" to get a - structure name. This works with all modules distributed with - Apache). - - <p>The lines between <code>ConfigStart</code> and - <code>ConfigEnd</code> as executed by <code>Configure</code> - and can be used to add compile-time options and libraries. In - this case it adds the DBM library (from $DBM_LIB) to the - standard compilation libraries ($LIB) and displays a - message.</p> - - <p>See the default distribution's mod_auth_dbm.c for an example - of an embedded module definition.</p> - - <h3>Module Definition Information for Binary Distribitions</h3> - If the module is to be distributed as binary (object or - library) rather than source, it is not possible to add the - module definition information to the source file. In this case - it can be placed in a separate file which has the same base - name as the object or library file, but with a - <code>.module</code> extension. So, for example, if the - distributed module object file is mod_demo.o, the module - definition file should be called mod_demo.module. It contains - the same information as above, but does not need to be inside a - C comment or delimited with - <code>MODULE-DEFINITION-START</code> <em>etc.</em> For example: - -<pre> -Name: demo_module -ConfigStart - LIBS="$LIBS $DBM_LIB" - if [ "X$DBM_LIB" != "X" ]; then - echo " + using $DBM_LIB for mod_demo" - fi -ConfigEnd -</pre> - See the default distribution's mod_auth_db.module for an - example of a separate module definition file. - <hr /> - - <h3 align="CENTER">Apache HTTP Server</h3> - <a href="./"><img src="images/index.gif" alt="Index" /></a> - - </body> -</html> - |