Return-Path: Delivered-To: apache-cvs-archive@hyperreal.org Received: (qmail 17918 invoked by uid 6000); 17 Sep 1998 14:15:06 -0000 Received: (qmail 17909 invoked by alias); 17 Sep 1998 14:15:04 -0000 Delivered-To: apache-1.3-cvs@hyperreal.org Received: (qmail 17907 invoked by uid 161); 17 Sep 1998 14:15:03 -0000 Date: 17 Sep 1998 14:15:03 -0000 Message-ID: <19980917141503.17906.qmail@hyperreal.org> From: coar@hyperreal.org To: apache-1.3-cvs@hyperreal.org Subject: cvs commit: apache-1.3/htdocs/manual/vhosts details.html examples.html host.html Sender: apache-cvs-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org coar 98/09/17 07:15:03 Modified: htdocs/manual content-negotiation.html custom-error.html dso.html ebcdic.html install.html invoking.html new_features_1_3.html sourcereorg.html upgrading_to_1_3.html windows.html htdocs/manual/misc API.html FAQ.html compat_notes.html custom_errordocs.html fin_wait_2.html howto.html nopgp.html perf-bsd44.html perf.html security_tips.html vif-info.html htdocs/manual/mod core.html mod_actions.html mod_asis.html mod_auth_anon.html mod_autoindex.html mod_isapi.html mod_mmap_static.html mod_proxy.html mod_rewrite.html htdocs/manual/vhosts details.html examples.html host.html Log: More documentation consistency cleanup for 1.3.2. Revision Changes Path 1.18 +5 -5 apache-1.3/htdocs/manual/content-negotiation.html Index: content-negotiation.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/content-negotiation.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- content-negotiation.html 1998/09/17 12:32:58 1.17 +++ content-negotiation.html 1998/09/17 14:14:47 1.18 @@ -85,7 +85,7 @@ ways: @@ -259,7 +260,7 @@

Information on creating loadable modules is also available.

-

  • Apache can also load ISAPI Extensions (i.e., Internet Server +

  • Apache can also load ISAPI Extensions (i.e., Internet Server Applications), such as those used by Microsoft's IIS, and other Windows servers. More information is available. @@ -359,7 +360,7 @@

    Compiling Apache requires Microsoft Visual C++ 5.0 to be properly installed. It is easiest to compile with the command-line tools - (nmake, etc...). Consult the VC++ manual to determine how to install + (nmake, etc...). Consult the VC++ manual to determine how to install them.

    First, unpack the Apache distribution into an appropriate 1.17 +12 -12 apache-1.3/htdocs/manual/misc/API.html Index: API.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/API.html,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- API.html 1998/05/20 14:22:39 1.16 +++ API.html 1998/09/17 14:14:52 1.17 @@ -14,7 +14,7 @@

    Apache API notes

    These are some notes on the Apache API and the data structures you -have to deal with, etc. They are not yet nearly complete, but +have to deal with, etc. They are not yet nearly complete, but hopefully, they will help you get your bearings. Keep in mind that the API is still subject to change as we gain experience with it. (See the TODO file for what might be coming). However, @@ -109,7 +109,7 @@ response phase is unique in that modules may declare multiple handlers for it, via a dispatch table keyed on the MIME type of the requested object. Modules may declare a response-phase handler which can handle -any request, by giving it the key */* (i.e., a +any request, by giving it the key */* (i.e., a wildcard MIME type specification). However, wildcard handlers are only invoked if the server has already tried and failed to find a more specific response handler for the MIME type of the requested object @@ -151,7 +151,7 @@ A final note on the declared types of the arguments of some of these commands: a pool is a pointer to a resource pool structure; these are used by the server to keep track of the memory -which has been allocated, files opened, etc., either to service a +which has been allocated, files opened, etc., either to service a particular request, or to handle the process of configuring itself. That way, when the request is over (or, for the configuration pool, when the server is restarting), the memory can be freed, and the files @@ -306,8 +306,8 @@ int header_only; /* HEAD request, as opposed to GET */ char *protocol; /* Protocol, as given to us, or HTTP/0.9 */ - char *method; /* GET, HEAD, POST, etc. */ - int method_number; /* M_GET, M_POST, etc. */ + char *method; /* GET, HEAD, POST, etc. */ + int method_number; /* M_GET, M_POST, etc. */ /* Info for logging */ @@ -325,7 +325,7 @@ * (the thing pointed to being the module's business). */ - void *per_dir_config; /* Options set in config files, etc. */ + void *per_dir_config; /* Options set in config files, etc. */ void *request_config; /* Notes on *this* request */ }; @@ -339,7 +339,7 @@ a few exceptions: 1.13 +2 -2 apache-1.3/htdocs/manual/misc/perf-bsd44.html Index: perf-bsd44.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/perf-bsd44.html,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- perf-bsd44.html 1998/05/29 15:33:19 1.12 +++ perf-bsd44.html 1998/09/17 14:14:53 1.13 @@ -63,7 +63,7 @@