From 80c32a1d5fe6458abcf83e4ca000eebcdb2c3da7 Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Thu, 5 Feb 1998 20:05:18 +0000 Subject: Another pass at the normalisation of the HTML tags. Some corrections coming up. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80130 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/bind.html | 10 ++--- docs/manual/bind.html.en | 10 ++--- docs/manual/cgi_path.html | 10 ++--- docs/manual/cgi_path.html.en | 10 ++--- docs/manual/content-negotiation.html | 26 ++++++------- docs/manual/content-negotiation.html.en | 26 ++++++------- docs/manual/custom-error.html | 2 +- docs/manual/custom-error.html.en | 2 +- docs/manual/developer/API.html | 44 +++++++++++----------- docs/manual/dns-caveats.html | 12 +++--- docs/manual/env.html | 2 +- docs/manual/env.html.en | 2 +- docs/manual/handler.html | 12 +++--- docs/manual/handler.html.en | 12 +++--- docs/manual/install.html | 4 +- docs/manual/install.html.en | 4 +- docs/manual/invoking.html | 18 ++++----- docs/manual/invoking.html.en | 18 ++++----- docs/manual/location.html | 2 +- docs/manual/misc/API.html | 44 +++++++++++----------- docs/manual/misc/client_block_api.html | 2 +- docs/manual/misc/custom_errordocs.html | 32 ++++++++-------- docs/manual/misc/howto.html | 2 +- docs/manual/misc/known_client_problems.html | 18 ++++----- docs/manual/misc/perf-tuning.html | 34 ++++++++--------- docs/manual/mod/core.html | 58 ++++++++++++++--------------- docs/manual/mod/mod_access.html | 6 +-- docs/manual/mod/mod_actions.html | 8 ++-- docs/manual/mod/mod_alias.html | 16 ++++---- docs/manual/mod/mod_asis.html | 4 +- docs/manual/mod/mod_auth.html | 6 +-- docs/manual/mod/mod_auth_anon.html | 26 ++++++------- docs/manual/mod/mod_auth_db.html | 6 +-- docs/manual/mod/mod_auth_dbm.html | 6 +-- docs/manual/mod/mod_autoindex.html | 30 +++++++-------- docs/manual/mod/mod_cern_meta.html | 10 ++--- docs/manual/mod/mod_cgi.html | 18 ++++----- docs/manual/mod/mod_dir.html | 6 +-- docs/manual/mod/mod_env.html | 10 ++--- docs/manual/mod/mod_headers.html | 8 ++-- docs/manual/mod/mod_imap.html | 26 ++++++------- docs/manual/mod/mod_include.html | 10 ++--- docs/manual/mod/mod_info.html | 2 +- docs/manual/mod/mod_isapi.html | 6 +-- docs/manual/mod/mod_log_agent.html | 2 +- docs/manual/mod/mod_log_config.html | 24 ++++++------ docs/manual/mod/mod_log_referer.html | 8 ++-- docs/manual/mod/mod_mime.html | 18 ++++----- docs/manual/mod/mod_mime_magic.html | 10 ++--- docs/manual/mod/mod_negotiation.html | 12 +++--- docs/manual/mod/mod_proxy.html | 54 +++++++++++++-------------- docs/manual/mod/mod_rewrite.html | 24 ++++++------ docs/manual/mod/mod_so.html | 8 ++-- docs/manual/mod/mod_speling.html | 6 +-- docs/manual/mod/mod_status.html | 12 +++--- docs/manual/mod/mod_unique_id.html | 4 +- docs/manual/mod/mod_userdir.html | 2 +- docs/manual/mod/mod_usertrack.html | 8 ++-- docs/manual/platform/perf.html | 2 +- docs/manual/platform/windows.html | 8 ++-- docs/manual/sections.html | 8 ++-- docs/manual/sections.html.en | 8 ++-- docs/manual/stopping.html | 10 ++--- docs/manual/stopping.html.en | 10 ++--- docs/manual/vhosts/details.html | 20 +++++----- docs/manual/vhosts/details_1_2.html | 10 ++--- docs/manual/vhosts/examples.html | 22 +++++------ docs/manual/vhosts/fd-limits.html | 2 +- docs/manual/vhosts/fd-limits.html.en | 2 +- docs/manual/vhosts/host.html | 10 ++--- docs/manual/vhosts/ip-based.html | 10 ++--- docs/manual/vhosts/name-based.html | 8 ++-- docs/manual/vhosts/name-based.html.en | 8 ++-- docs/manual/vhosts/vhosts-in-depth.html | 10 ++--- docs/manual/vhosts/virtual-host.html | 12 +++--- 75 files changed, 486 insertions(+), 486 deletions(-) (limited to 'docs') diff --git a/docs/manual/bind.html b/docs/manual/bind.html index d5caf449fa..acbe645e3b 100644 --- a/docs/manual/bind.html +++ b/docs/manual/bind.html @@ -12,7 +12,7 @@ ALINK="#FF0000" > -

Setting which addresses and ports Apache uses

+

Setting which addresses and ports Apache uses

@@ -36,7 +36,7 @@ and ports Apache listens to. to more than one address and/or port. -

BindAddress

+

BindAddress

Port directive. Only one BindAddress should be used. -

Listen

+

Listen

-

How this works with Virtual Hosts

+

How this works with Virtual Hosts

BindAddress and Listen do not implement Virtual Hosts. They tell the main server what addresses and ports to listen to. If no @@ -116,7 +116,7 @@ and port to set the behavior of this virtual host. Note that if the <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed. -

See also

+

See also

See also the documentation on Virtual Hosts, diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index d5caf449fa..acbe645e3b 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -12,7 +12,7 @@ ALINK="#FF0000" > -

Setting which addresses and ports Apache uses

+

Setting which addresses and ports Apache uses

@@ -36,7 +36,7 @@ and ports Apache listens to. to more than one address and/or port. -

BindAddress

+

BindAddress

Port directive. Only one BindAddress should be used. -

Listen

+

Listen

-

How this works with Virtual Hosts

+

How this works with Virtual Hosts

BindAddress and Listen do not implement Virtual Hosts. They tell the main server what addresses and ports to listen to. If no @@ -116,7 +116,7 @@ and port to set the behavior of this virtual host. Note that if the <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed. -

See also

+

See also

See also the documentation on Virtual Hosts, diff --git a/docs/manual/cgi_path.html b/docs/manual/cgi_path.html index ed95efcd42..569ddbb343 100644 --- a/docs/manual/cgi_path.html +++ b/docs/manual/cgi_path.html @@ -12,11 +12,11 @@ ALINK="#FF0000" > -

PATH_INFO Changes in the CGI Environment

+

PATH_INFO Changes in the CGI Environment

-

Overview

+

Overview

As implemented in Apache 1.1.1 and earlier versions, the method Apache used to create PATH_INFO in the CGI environment was @@ -27,7 +27,7 @@ applications, the Apache 1.2 behavior is still compatible with the CGI/1.1 specification, and CGI scripts can be easily modified (see below). -

The Problem

+

The Problem

Apache 1.1.1 and earlier implemented the PATH_INFO and SCRIPT_NAME environment variables by looking at the filename, not the URL. While @@ -46,7 +46,7 @@ SCRIPT_NAME to "/cgi-". Obviously, the latter is incorrect. In certain cases, this could even cause the server to crash.

-

The Solution

+

The Solution

Apache 1.2 and later now determine SCRIPT_NAME and PATH_INFO by looking directly at the URL, and determining how much of the URL is @@ -67,7 +67,7 @@ sort of information is not a recommended method, and a script making use of it "deserves" not to work. Apache 1.2b3 and later, however, do provide a workaround. -

Compatibility with Previous Servers

+

Compatibility with Previous Servers

It may be necessary for a script that was designed for earlier versions of Apache or other servers to need the information that the diff --git a/docs/manual/cgi_path.html.en b/docs/manual/cgi_path.html.en index ed95efcd42..569ddbb343 100644 --- a/docs/manual/cgi_path.html.en +++ b/docs/manual/cgi_path.html.en @@ -12,11 +12,11 @@ ALINK="#FF0000" > -

PATH_INFO Changes in the CGI Environment

+

PATH_INFO Changes in the CGI Environment

-

Overview

+

Overview

As implemented in Apache 1.1.1 and earlier versions, the method Apache used to create PATH_INFO in the CGI environment was @@ -27,7 +27,7 @@ applications, the Apache 1.2 behavior is still compatible with the CGI/1.1 specification, and CGI scripts can be easily modified (see below). -

The Problem

+

The Problem

Apache 1.1.1 and earlier implemented the PATH_INFO and SCRIPT_NAME environment variables by looking at the filename, not the URL. While @@ -46,7 +46,7 @@ SCRIPT_NAME to "/cgi-". Obviously, the latter is incorrect. In certain cases, this could even cause the server to crash.

-

The Solution

+

The Solution

Apache 1.2 and later now determine SCRIPT_NAME and PATH_INFO by looking directly at the URL, and determining how much of the URL is @@ -67,7 +67,7 @@ sort of information is not a recommended method, and a script making use of it "deserves" not to work. Apache 1.2b3 and later, however, do provide a workaround. -

Compatibility with Previous Servers

+

Compatibility with Previous Servers

It may be necessary for a script that was designed for earlier versions of Apache or other servers to need the information that the diff --git a/docs/manual/content-negotiation.html b/docs/manual/content-negotiation.html index 2a0abb5ccd..98e0190677 100644 --- a/docs/manual/content-negotiation.html +++ b/docs/manual/content-negotiation.html @@ -13,7 +13,7 @@ ALINK="#FF0000" > -

Content Negotiation

+

Content Negotiation

Apache's support for content negotiation has been updated to meet the @@ -29,7 +29,7 @@ which is compiled in by default.

-

About Content Negotiation

+

About Content Negotiation

A resource may be available in several different representations. For @@ -77,7 +77,7 @@ available in several formats, these are called representations or variants. The ways in which the variants for a particular resource vary are called the dimensions of negotiation. -

Negotiation in Apache

+

Negotiation in Apache

In order to negotiate a resource, the server needs to be given @@ -91,7 +91,7 @@ ways: filename pattern match, and chooses from among the results. -

Using a type-map file

+

Using a type-map file

A type map is a document which is associated with the handler @@ -182,7 +182,7 @@ The full list of headers recognized is: thresholds without checking the actual file. -

Multiviews

+

Multiviews

This is a per-directory option, meaning it can be set with an @@ -229,7 +229,7 @@ rating, and generally invoked; otherwise it is given an extremely low quality rating, which generally causes one of the other views (if any) to be retrieved. -

The Negotiation Algorithm

+

The Negotiation Algorithm

After Apache has obtained a list of the variants for a given resource, either from a type-map file or from the filenames in the directory, it @@ -244,7 +244,7 @@ In some circumstances, Apache can 'fiddle' the quality factor of a particular dimension to achieve a better result. The ways Apache can fiddle quality factors is explained in more detail below. -

Dimensions of Negotiation

+

Dimensions of Negotiation

Dimension @@ -265,7 +265,7 @@ or more languages. can indicate a charset as a parameter of the media type.
-

Apache Negotiation Algorithm

+

Apache Negotiation Algorithm

Apache uses an algorithm to select the 'best' variant (if any) to @@ -330,7 +330,7 @@ and go to stage 3. -

Fiddling with Quality Values

+

Fiddling with Quality Values

Apache sometimes changes the quality values from what would be @@ -343,7 +343,7 @@ sends full and correct information these fiddles will not be applied.

-

Media Types and Wildcards

+

Media Types and Wildcards

The Accept: request header indicates preferences for media types. It @@ -386,7 +386,7 @@ behavior. It also sets the q value of wildcards of the format these special values are not applied, so requests from browsers which send the correct information to start with work as expected. -

Variants with no Language

+

Variants with no Language

If some of the variants for a particular resource have a language @@ -413,7 +413,7 @@ header includes either en or fr (or both) one of foo.en.html or foo.fr.html will be returned. If the browser does not list either en or fr as acceptable, foo.html will be returned instead. -

Note on hyperlinks and naming conventions

+

Note on hyperlinks and naming conventions

If you are using language negotiation you can choose between @@ -500,7 +500,7 @@ if there is one) must be on the right hand side of the mime-type extension (e.g. foo.html.en). -

Note on Caching

+

Note on Caching

When a cache stores a document, it associates it with the request URL. diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en index 2a0abb5ccd..98e0190677 100644 --- a/docs/manual/content-negotiation.html.en +++ b/docs/manual/content-negotiation.html.en @@ -13,7 +13,7 @@ ALINK="#FF0000" > -

Content Negotiation

+

Content Negotiation

Apache's support for content negotiation has been updated to meet the @@ -29,7 +29,7 @@ which is compiled in by default.

-

About Content Negotiation

+

About Content Negotiation

A resource may be available in several different representations. For @@ -77,7 +77,7 @@ available in several formats, these are called representations or variants. The ways in which the variants for a particular resource vary are called the dimensions of negotiation. -

Negotiation in Apache

+

Negotiation in Apache

In order to negotiate a resource, the server needs to be given @@ -91,7 +91,7 @@ ways: filename pattern match, and chooses from among the results. -

Using a type-map file

+

Using a type-map file

A type map is a document which is associated with the handler @@ -182,7 +182,7 @@ The full list of headers recognized is: thresholds without checking the actual file. -

Multiviews

+

Multiviews

This is a per-directory option, meaning it can be set with an @@ -229,7 +229,7 @@ rating, and generally invoked; otherwise it is given an extremely low quality rating, which generally causes one of the other views (if any) to be retrieved. -

The Negotiation Algorithm

+

The Negotiation Algorithm

After Apache has obtained a list of the variants for a given resource, either from a type-map file or from the filenames in the directory, it @@ -244,7 +244,7 @@ In some circumstances, Apache can 'fiddle' the quality factor of a particular dimension to achieve a better result. The ways Apache can fiddle quality factors is explained in more detail below. -

Dimensions of Negotiation

+

Dimensions of Negotiation

Dimension @@ -265,7 +265,7 @@ or more languages. can indicate a charset as a parameter of the media type.
-

Apache Negotiation Algorithm

+

Apache Negotiation Algorithm

Apache uses an algorithm to select the 'best' variant (if any) to @@ -330,7 +330,7 @@ and go to stage 3. -

Fiddling with Quality Values

+

Fiddling with Quality Values

Apache sometimes changes the quality values from what would be @@ -343,7 +343,7 @@ sends full and correct information these fiddles will not be applied.

-

Media Types and Wildcards

+

Media Types and Wildcards

The Accept: request header indicates preferences for media types. It @@ -386,7 +386,7 @@ behavior. It also sets the q value of wildcards of the format these special values are not applied, so requests from browsers which send the correct information to start with work as expected. -

Variants with no Language

+

Variants with no Language

If some of the variants for a particular resource have a language @@ -413,7 +413,7 @@ header includes either en or fr (or both) one of foo.en.html or foo.fr.html will be returned. If the browser does not list either en or fr as acceptable, foo.html will be returned instead. -

Note on hyperlinks and naming conventions

+

Note on hyperlinks and naming conventions

If you are using language negotiation you can choose between @@ -500,7 +500,7 @@ if there is one) must be on the right hand side of the mime-type extension (e.g. foo.html.en). -

Note on Caching

+

Note on Caching

When a cache stores a document, it associates it with the request URL. diff --git a/docs/manual/custom-error.html b/docs/manual/custom-error.html index 802bd5cbe3..5e2a3a9475 100644 --- a/docs/manual/custom-error.html +++ b/docs/manual/custom-error.html @@ -114,7 +114,7 @@ ErrorDocument 401 /Subscription/how_to_subscribe.html

-

Custom error responses and redirects

+

Custom error responses and redirects

diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en index 802bd5cbe3..5e2a3a9475 100644 --- a/docs/manual/custom-error.html.en +++ b/docs/manual/custom-error.html.en @@ -114,7 +114,7 @@ ErrorDocument 401 /Subscription/how_to_subscribe.html

-

Custom error responses and redirects

+

Custom error responses and redirects

diff --git a/docs/manual/developer/API.html b/docs/manual/developer/API.html index fdcd8737a3..4b47d48791 100644 --- a/docs/manual/developer/API.html +++ b/docs/manual/developer/API.html @@ -11,7 +11,7 @@ ALINK="#FF0000" > -

Apache API notes

+

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 @@ -57,12 +57,12 @@ coming up, and in what order: -

Basic concepts.

+

Basic concepts.

We begin with an overview of the basic concepts behind the API, and how they are manifested in the code. -

Handlers, Modules, and Requests

+

Handlers, Modules, and Requests

Apache breaks down request handling into a series of steps, more or less the same way the Netscape server API does (although this API has @@ -116,7 +116,7 @@ The handlers themselves are functions of one argument (a request_rec structure. vide infra), which returns an integer, as above.

-

A brief tour of a module

+

A brief tour of a module

At this point, we need to explain the structure of a module. Our candidate will be one of the messier ones, the CGI module --- this @@ -215,14 +215,14 @@ module cgi_module = { }; -

How handlers work

+

How handlers work

The sole argument to handlers is a request_rec structure. This structure describes a particular request which has been made to the server, on behalf of a client. In most cases, each connection to the client generates only one request_rec structure.

-

A brief tour of the request_rec

+

A brief tour of the request_rec

The request_rec contains pointers to a resource pool which will be cleared when the server is finished handling the @@ -329,7 +329,7 @@ struct request_rec { -

Where request_rec structures come from

+

Where request_rec structures come from

Most request_rec structures are built by reading an HTTP request from a client, and filling in the fields. However, there are @@ -370,7 +370,7 @@ a few exceptions: function run_sub_request). -

Handling requests, declining, and returning error codes

+

Handling requests, declining, and returning error codes

As discussed above, each handler, when invoked to handle a particular request_rec, has to return an int to @@ -389,7 +389,7 @@ the module should put a Location in the request's headers_out, to indicate where the client should be redirected to.

-

Special considerations for response handlers

+

Special considerations for response handlers

Handlers for most phases do their work by simply setting a few fields in the request_rec structure (or, in the case of access @@ -463,7 +463,7 @@ internally redirected should always return OK.

(Invoking internal_redirect from handlers which are not response handlers will lead to serious confusion). -

Special considerations for authentication handlers

+

Special considerations for authentication handlers

Stuff that should be discussed here in detail: @@ -481,7 +481,7 @@ Stuff that should be discussed here in detail: to be sent back). -

Special considerations for logging handlers

+

Special considerations for logging handlers

When a request has internally redirected, there is the question of what to log. Apache handles this by bundling the entire chain of @@ -493,7 +493,7 @@ initial request from the client; note that the bytes_sent field will only be correct in the last request in the chain (the one for which a response was actually sent). -

Resource allocation and resource pools

+

Resource allocation and resource pools

One of the problems of writing and designing a server-pool server is that of preventing leakage, that is, allocating resources (memory, @@ -544,7 +544,7 @@ We begin here by describing how memory is allocated to pools, and then discuss how other resources are tracked by the resource pool machinery. -

Allocation of memory in pools

+

Allocation of memory in pools

Memory is allocated to pools by calling the function palloc, which takes two arguments, one being a pointer to @@ -583,7 +583,7 @@ sub-pools below, and is used in the directory-indexing code, in order to avoid excessive storage allocation when listing directories with thousands of files). -

Allocating initialized memory

+

Allocating initialized memory

There are functions which allocate initialized memory, and are frequently useful. The function pcalloc has the same @@ -604,7 +604,7 @@ of the strings, as a unit; for instance: returns a pointer to 8 bytes worth of memory, initialized to "foo/bar". -

Tracking open files, etc.

+

Tracking open files, etc.

As indicated above, resource pools are also used to track other sorts of resources besides memory. The most common are open files. The @@ -638,13 +638,13 @@ systems such as Linux, which react badly if the same file will eventually be closed regardless, but you should consider it in cases where your module is opening, or could open, a lot of files). -

Other sorts of resources --- cleanup functions

+

Other sorts of resources --- cleanup functions

More text goes here. Describe the the cleanup primitives in terms of which the file stuff is implemented; also, spawn_process. -

Fine control --- creating and dealing with sub-pools, with a note -on sub-requests

+

Fine control --- creating and dealing with sub-pools, with a note +on sub-requests

On rare occasions, too-free use of palloc() and the associated primitives may result in undesirably profligate resource @@ -686,7 +686,7 @@ cleared. It is only when you are allocating many, many sub-requests for a single main request that you should seriously consider the destroy... functions). -

Configuration, commands and the like

+

Configuration, commands and the like

One of the design goals for this server was to maintain external compatibility with the NCSA 1.3 server --- that is, to read the same @@ -735,7 +735,7 @@ for handling them. That is solved the same way it is solved wherever else similar problems come up, by tying those structures to the per-transaction resource pool.

-

Per-directory configuration structures

+

Per-directory configuration structures

Let's look out how all of this plays out in mod_mime.c, which defines the file typing handler which emulates the NCSA server's @@ -828,7 +828,7 @@ consists solely of the state of the XBITHACK), and for those modules, you can just not declare one, and leave the corresponding structure slot in the module itself NULL.

-

Command handling

+

Command handling

Now that we have these structures, we need to be able to figure out how to fill them. That involves processing the actual @@ -967,7 +967,7 @@ int find_ct(request_rec *r) -

Side notes --- per-server configuration, virtual servers, etc.

+

Side notes --- per-server configuration, virtual servers, etc.

The basic ideas behind per-server module configuration are basically the same as those for per-directory configuration; there is a creation diff --git a/docs/manual/dns-caveats.html b/docs/manual/dns-caveats.html index 4e9719df3b..530573fc79 100644 --- a/docs/manual/dns-caveats.html +++ b/docs/manual/dns-caveats.html @@ -12,7 +12,7 @@ ALINK="#FF0000" > -

Issues Regarding DNS and Apache

+

Issues Regarding DNS and Apache

This page could be summarized with the statement: don't require Apache to use DNS for any parsing of the configuration files. @@ -21,7 +21,7 @@ server may be subject to reliability problems (it might not boot), or denial and theft of service attacks (including users able to steal hits from other users). -

A Simple Example

+

A Simple Example

Consider this configuration snippet: @@ -71,7 +71,7 @@ which includes the server name then it will fail to generate a valid URL. </VirtualHost> -

Denial of Service

+

Denial of Service

There are (at least) two forms that denial of service can come in. If you are running a version of Apache prior to version 1.2 then your @@ -115,7 +115,7 @@ this happens requires a more in-depth discussion of how Apache matches up incoming requests with the virtual host that will serve it. A rough document describing this is available. -

The "main server" Address

+

The "main server" Address

The addition of name-based virtual host support in Apache 1.1 requires Apache to know the IP address(es) of @@ -141,7 +141,7 @@ CGIs unless you use mod_env to control the environment. It's best to consult the man pages or FAQs for your OS. -

Tips to Avoid these problems

+

Tips to Avoid these problems

  • use IP addresses in <VirtualHost> @@ -152,7 +152,7 @@ for your OS. has no pages to serve
-

Appendix: Future Directions

+

Appendix: Future Directions

The situation regarding DNS is highly undesirable. For Apache 1.2 we've attempted to make the server at least continue booting diff --git a/docs/manual/env.html b/docs/manual/env.html index 6fd778adaa..6235076c4c 100644 --- a/docs/manual/env.html +++ b/docs/manual/env.html @@ -13,7 +13,7 @@ ALINK="#FF0000" > -

Special Purpose Environment Variables

+

Special Purpose Environment Variables

Interoperability problems have led to the introduction of mechanisms to modify the way Apache behaves when talking to particular clients. To make these mechanisms as flexible as possible, they diff --git a/docs/manual/env.html.en b/docs/manual/env.html.en index 6fd778adaa..6235076c4c 100644 --- a/docs/manual/env.html.en +++ b/docs/manual/env.html.en @@ -13,7 +13,7 @@ ALINK="#FF0000" > -

Special Purpose Environment Variables

+

Special Purpose Environment Variables

Interoperability problems have led to the introduction of mechanisms to modify the way Apache behaves when talking to particular clients. To make these mechanisms as flexible as possible, they diff --git a/docs/manual/handler.html b/docs/manual/handler.html index a87b4d319d..d5995da06b 100644 --- a/docs/manual/handler.html +++ b/docs/manual/handler.html @@ -13,9 +13,9 @@ ALINK="#FF0000" > -

Apache's Handler Use

+

Apache's Handler Use

-

What is a Handler

+

What is a Handler

A "handler" is an internal Apache representation of the action to be performed when a file is called. Generally, files have implicit @@ -61,7 +61,7 @@ handlers in the standard distribution are as follows:

-

Directives

+

Directives

  • AddHandler
  • SetHandler @@ -69,7 +69,7 @@ handlers in the standard distribution are as follows:

    -

    AddHandler

    +

    AddHandler

    -

    SetHandler

    +

    SetHandler

    -

    Programmer's Note

    +

    Programmer's Note

    In order to implement the handler features, an addition has been made to the Apache API that you may wish to diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index a87b4d319d..d5995da06b 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -13,9 +13,9 @@ ALINK="#FF0000" > -

    Apache's Handler Use

    +

    Apache's Handler Use

    -

    What is a Handler

    +

    What is a Handler

    A "handler" is an internal Apache representation of the action to be performed when a file is called. Generally, files have implicit @@ -61,7 +61,7 @@ handlers in the standard distribution are as follows:

    -

    Directives

    +

    Directives

    • AddHandler
    • SetHandler @@ -69,7 +69,7 @@ handlers in the standard distribution are as follows:

      -

      AddHandler

      +

      AddHandler

      -

      SetHandler

      +

      SetHandler

      -

      Programmer's Note

      +

      Programmer's Note

      In order to implement the handler features, an addition has been made to the Apache API that you may wish to diff --git a/docs/manual/install.html b/docs/manual/install.html index e799ad0bac..33878db24d 100644 --- a/docs/manual/install.html +++ b/docs/manual/install.html @@ -33,7 +33,7 @@ If you downloaded a binary distribution, skip to Installing Apache. Otherwise read the next section for how to compile the server. -

      Compiling Apache

      +

      Compiling Apache

      Compiling Apache consists of three steps: Firstly select which Apache modules you want to include into the server. Secondly create a @@ -115,7 +115,7 @@ HREF="http://www.apache.org/dist/contrib/modules/"><URL:http://www.apache.org There are instructions on that page for linking these modules into the core Apache code. -

      Installing Apache

      +

      Installing Apache

      You will have a binary file called httpd in the src directory. A binary distribution of Apache will diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index e799ad0bac..33878db24d 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -33,7 +33,7 @@ If you downloaded a binary distribution, skip to Installing Apache. Otherwise read the next section for how to compile the server. -

      Compiling Apache

      +

      Compiling Apache

      Compiling Apache consists of three steps: Firstly select which Apache modules you want to include into the server. Secondly create a @@ -115,7 +115,7 @@ HREF="http://www.apache.org/dist/contrib/modules/"><URL:http://www.apache.org There are instructions on that page for linking these modules into the core Apache code. -

      Installing Apache

      +

      Installing Apache

      You will have a binary file called httpd in the src directory. A binary distribution of Apache will diff --git a/docs/manual/invoking.html b/docs/manual/invoking.html index d718c2f89c..1eff24f2d1 100644 --- a/docs/manual/invoking.html +++ b/docs/manual/invoking.html @@ -13,9 +13,9 @@ ALINK="#FF0000" > -

      Starting Apache

      +

      Starting Apache

      -

      Invoking Apache

      +

      Invoking Apache

      The httpd program is usually run as a daemon which executes continuously, handling requests. It is possible to invoke Apache by the Internet daemon inetd each time a connection to the HTTP @@ -23,7 +23,7 @@ service is made (use the ServerType directive) but this is not recommended. -

      Command line options

      +

      Command line options

      The following options are recognized on the httpd command line:
      -d serverroot @@ -63,7 +63,7 @@ places where the directive is valid. (New in Apache 1.2)
      Print a list of the httpd options, and then exit.
      -

      Configuration files

      +

      Configuration files

      The server will read three files for configuration directives. Any directive may appear in any of these files. The the names of these files are taken to be relative to the server root; this is set by the @@ -92,15 +92,15 @@ The server also reads a file containing mime document types; the filename is set by the TypesConfig directive, and is conf/mime.types by default. -

      Log files

      -

      security warning

      +

      Log files

      +

      security warning

      Anyone who can write to the directory where Apache is writing a log file can almost certainly gain access to the uid that the server is started as, which is normally root. Do NOT give people write access to the directory the logs are stored in without being aware of the consequences; see the security tips document for details. -

      pid file

      +

      pid file

      On daemon startup, it saves the process id of the parent httpd process to the file logs/httpd.pid. This filename can be changed with the PidFile directive. The process-id is for @@ -112,13 +112,13 @@ see the Stopping and Restarting page. If the process dies (or is killed) abnormally, then it will be necessary to kill the children httpd processes. -

      Error log

      +

      Error log

      The server will log error messages to a log file, logs/error_log by default. The filename can be set using the ErrorLog directive; different error logs can be set for different virtual hosts. -

      Transfer log

      +

      Transfer log

      The server will typically log each request to a transfer file, logs/access_log by default. The filename can be set using a TransferLog directive; different diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en index d718c2f89c..1eff24f2d1 100644 --- a/docs/manual/invoking.html.en +++ b/docs/manual/invoking.html.en @@ -13,9 +13,9 @@ ALINK="#FF0000" > -

      Starting Apache

      +

      Starting Apache

      -

      Invoking Apache

      +

      Invoking Apache

      The httpd program is usually run as a daemon which executes continuously, handling requests. It is possible to invoke Apache by the Internet daemon inetd each time a connection to the HTTP @@ -23,7 +23,7 @@ service is made (use the ServerType directive) but this is not recommended. -

      Command line options

      +

      Command line options

      The following options are recognized on the httpd command line:
      -d serverroot @@ -63,7 +63,7 @@ places where the directive is valid. (New in Apache 1.2)
      Print a list of the httpd options, and then exit.
      -

      Configuration files

      +

      Configuration files

      The server will read three files for configuration directives. Any directive may appear in any of these files. The the names of these files are taken to be relative to the server root; this is set by the @@ -92,15 +92,15 @@ The server also reads a file containing mime document types; the filename is set by the TypesConfig directive, and is conf/mime.types by default. -

      Log files

      -

      security warning

      +

      Log files

      +

      security warning

      Anyone who can write to the directory where Apache is writing a log file can almost certainly gain access to the uid that the server is started as, which is normally root. Do NOT give people write access to the directory the logs are stored in without being aware of the consequences; see the security tips document for details. -

      pid file

      +

      pid file

      On daemon startup, it saves the process id of the parent httpd process to the file logs/httpd.pid. This filename can be changed with the PidFile directive. The process-id is for @@ -112,13 +112,13 @@ see the Stopping and Restarting page. If the process dies (or is killed) abnormally, then it will be necessary to kill the children httpd processes. -

      Error log

      +

      Error log

      The server will log error messages to a log file, logs/error_log by default. The filename can be set using the ErrorLog directive; different error logs can be set for different virtual hosts. -

      Transfer log

      +

      Transfer log

      The server will typically log each request to a transfer file, logs/access_log by default. The filename can be set using a TransferLog directive; different diff --git a/docs/manual/location.html b/docs/manual/location.html index e8063f12fe..85552c9cfe 100644 --- a/docs/manual/location.html +++ b/docs/manual/location.html @@ -15,7 +15,7 @@

      Access Control by URL

      -

      The <Location> Directive

      +

      The <Location> Directive

      -

      Apache API notes

      +

      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 @@ -57,12 +57,12 @@ coming up, and in what order:
    -

    Basic concepts.

    +

    Basic concepts.

    We begin with an overview of the basic concepts behind the API, and how they are manifested in the code. -

    Handlers, Modules, and Requests

    +

    Handlers, Modules, and Requests

    Apache breaks down request handling into a series of steps, more or less the same way the Netscape server API does (although this API has @@ -116,7 +116,7 @@ The handlers themselves are functions of one argument (a request_rec structure. vide infra), which returns an integer, as above.

    -

    A brief tour of a module

    +

    A brief tour of a module

    At this point, we need to explain the structure of a module. Our candidate will be one of the messier ones, the CGI module --- this @@ -215,14 +215,14 @@ module cgi_module = { }; -

    How handlers work

    +

    How handlers work

    The sole argument to handlers is a request_rec structure. This structure describes a particular request which has been made to the server, on behalf of a client. In most cases, each connection to the client generates only one request_rec structure.

    -

    A brief tour of the request_rec

    +

    A brief tour of the request_rec

    The request_rec contains pointers to a resource pool which will be cleared when the server is finished handling the @@ -329,7 +329,7 @@ struct request_rec { -

    Where request_rec structures come from

    +

    Where request_rec structures come from

    Most request_rec structures are built by reading an HTTP request from a client, and filling in the fields. However, there are @@ -370,7 +370,7 @@ a few exceptions: function run_sub_request).
-

Handling requests, declining, and returning error codes

+

Handling requests, declining, and returning error codes

As discussed above, each handler, when invoked to handle a particular request_rec, has to return an int to @@ -389,7 +389,7 @@ the module should put a Location in the request's headers_out, to indicate where the client should be redirected to.

-

Special considerations for response handlers

+

Special considerations for response handlers

Handlers for most phases do their work by simply setting a few fields in the request_rec structure (or, in the case of access @@ -463,7 +463,7 @@ internally redirected should always return OK.

(Invoking internal_redirect from handlers which are not response handlers will lead to serious confusion). -

Special considerations for authentication handlers

+

Special considerations for authentication handlers

Stuff that should be discussed here in detail: @@ -481,7 +481,7 @@ Stuff that should be discussed here in detail: to be sent back). -

Special considerations for logging handlers

+

Special considerations for logging handlers

When a request has internally redirected, there is the question of what to log. Apache handles this by bundling the entire chain of @@ -493,7 +493,7 @@ initial request from the client; note that the bytes_sent field will only be correct in the last request in the chain (the one for which a response was actually sent). -

Resource allocation and resource pools

+

Resource allocation and resource pools

One of the problems of writing and designing a server-pool server is that of preventing leakage, that is, allocating resources (memory, @@ -544,7 +544,7 @@ We begin here by describing how memory is allocated to pools, and then discuss how other resources are tracked by the resource pool machinery. -

Allocation of memory in pools

+

Allocation of memory in pools

Memory is allocated to pools by calling the function palloc, which takes two arguments, one being a pointer to @@ -583,7 +583,7 @@ sub-pools below, and is used in the directory-indexing code, in order to avoid excessive storage allocation when listing directories with thousands of files). -

Allocating initialized memory

+

Allocating initialized memory

There are functions which allocate initialized memory, and are frequently useful. The function pcalloc has the same @@ -604,7 +604,7 @@ of the strings, as a unit; for instance: returns a pointer to 8 bytes worth of memory, initialized to "foo/bar". -

Tracking open files, etc.

+

Tracking open files, etc.

As indicated above, resource pools are also used to track other sorts of resources besides memory. The most common are open files. The @@ -638,13 +638,13 @@ systems such as Linux, which react badly if the same file will eventually be closed regardless, but you should consider it in cases where your module is opening, or could open, a lot of files). -

Other sorts of resources --- cleanup functions

+

Other sorts of resources --- cleanup functions

More text goes here. Describe the the cleanup primitives in terms of which the file stuff is implemented; also, spawn_process. -

Fine control --- creating and dealing with sub-pools, with a note -on sub-requests

+

Fine control --- creating and dealing with sub-pools, with a note +on sub-requests

On rare occasions, too-free use of palloc() and the associated primitives may result in undesirably profligate resource @@ -686,7 +686,7 @@ cleared. It is only when you are allocating many, many sub-requests for a single main request that you should seriously consider the destroy... functions). -

Configuration, commands and the like

+

Configuration, commands and the like

One of the design goals for this server was to maintain external compatibility with the NCSA 1.3 server --- that is, to read the same @@ -735,7 +735,7 @@ for handling them. That is solved the same way it is solved wherever else similar problems come up, by tying those structures to the per-transaction resource pool.

-

Per-directory configuration structures

+

Per-directory configuration structures

Let's look out how all of this plays out in mod_mime.c, which defines the file typing handler which emulates the NCSA server's @@ -828,7 +828,7 @@ consists solely of the state of the XBITHACK), and for those modules, you can just not declare one, and leave the corresponding structure slot in the module itself NULL.

-

Command handling

+

Command handling

Now that we have these structures, we need to be able to figure out how to fill them. That involves processing the actual @@ -967,7 +967,7 @@ int find_ct(request_rec *r) -

Side notes --- per-server configuration, virtual servers, etc.

+

Side notes --- per-server configuration, virtual servers, etc.

The basic ideas behind per-server module configuration are basically the same as those for per-directory configuration; there is a creation diff --git a/docs/manual/misc/client_block_api.html b/docs/manual/misc/client_block_api.html index 4f65341af6..8f89d1ad6e 100644 --- a/docs/manual/misc/client_block_api.html +++ b/docs/manual/misc/client_block_api.html @@ -30,7 +30,7 @@ accomplished while remaining backwards-compatible.

-

The New API Functions

+

The New API Functions

    int setup_client_block (request_rec *, int read_policy);
diff --git a/docs/manual/misc/custom_errordocs.html b/docs/manual/misc/custom_errordocs.html
index dfc669dd4f..93b144c32d 100644
--- a/docs/manual/misc/custom_errordocs.html
+++ b/docs/manual/misc/custom_errordocs.html
@@ -1,8 +1,8 @@
 
-
-
-International Customized Server Error Messages
-
+
+
+International Customized Server Error Messages
+
 
 
 The AddHandler and
      AddType directives are useful
      for automatically XSSI-expanding all files with a .shtml
-     suffix to text/html.
+     suffix to text/html.
  
  • By using the Alias directive,
      we keep the error document directory outside of the document tree
      because it can be regarded more as a server part than part of
@@ -119,7 +119,7 @@ of as much server support as we can get:
      Note that we only define the basename of the document here
      because the MultiViews option will select the best candidate
      based on the language suffixes and the client's preferences.
-     Any error situation with an error code not handled by a
+     Any error situation with an error code not handled by a
      custom document will be dealt with by the server in the standard way
      (i.e., a plain error message in english).
  
  • Finally, the AllowOverride
@@ -128,12 +128,12 @@ of as much server support as we can get:
      optimization.
 
 The resulting httpd.conf configuration would the look
-similar to this: (Note that you can defrine your own error
+similar to this: (Note that you can defrine your own error
 messages using this method for only part of the document tree,
 e.g., a /~user/ subtree. In this case, the configuration could as well
 be put into the .htaccess file at the root of the subtree. In this case,
 the <Directory> and </Directory> directives -but not
-the contained directives- must be omitted.)
+the contained directives- must be omitted.)
 
       LanguagePriority en fr de 
   Alias  /errordocs  /usr/local/apache/errordocs
@@ -176,9 +176,9 @@ the configured error documents):
      would be bypassed.
  
  • For each language for which we have a translation (note that this need not
      be the same set of languages for each error code - you can get by
-     with a single language version until you actually have
+     with a single language version until you actually have
      translated versions), a document
-     errordocs/403.shtml.lang is created and
+     errordocs/403.shtml.lang is created and
      filled with the error text in that language (see
      below).
  
  • One fallback document called errordocs/403.shtml is
@@ -214,9 +214,9 @@ because it contains server-parsed content but no language specific
 information. The footer file exists once for each language translation,
 plus a symlink for the default language.
    
 Example: for english, french and german versions (default english)
    
-foot.shtml.en,
    
-foot.shtml.fr,
    
-foot.shtml.de,
    
+foot.shtml.en,
    
+foot.shtml.fr,
    
+foot.shtml.de,
    
 foot.shtml symlink to foot.shtml.en
    
 Both files are then simply included into the error document by using the
 directives <!--#include virtual="head" -->
@@ -377,13 +377,13 @@ for browser types which support animated GIFs).
 
 
    More welcome!
    
 
-If you have tips to contribute, send mail to Martin.Kraemer@Mch.SNI.De
+If you have tips to contribute, send mail to Martin.Kraemer@Mch.SNI.De
 
 
    
 
 Index
 Home
 
-
+
 
diff --git a/docs/manual/misc/howto.html b/docs/manual/misc/howto.html
index 0fa77d96be..2eb207ad52 100644
--- a/docs/manual/misc/howto.html
+++ b/docs/manual/misc/howto.html
@@ -55,7 +55,7 @@ This will send an HTTP 302 Redirect back to the client, and no matter
 what they gave in the original URL, they'll be sent to
 "http://www.apache.org".
 
-The second option is to set up a ScriptAlias pointing to
+The second option is to set up a ScriptAlias pointing to
 a cgi script which outputs a 301 or 302 status and the location
 of the other server.
    
 
diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html
index 59de0de7bb..cb102b4103 100644
--- a/docs/manual/misc/known_client_problems.html
+++ b/docs/manual/misc/known_client_problems.html
@@ -49,7 +49,7 @@ is not included in the Content-Length of the request.
 Apache works around this problem by eating any empty lines which
 appear before a request.
 
-
    Broken keepalive
    
+
    Broken keepalive
    
 
 
    Various clients have had broken implementations of keepalive
 (persistent connections).  In particular the Windows versions of
@@ -72,7 +72,7 @@ patch to version 1.2.1.  Then add this to your config:
 BrowserMatch "MSIE 4\.0b2;" nokeepalive
 
 
-
    Incorrect interpretation of HTTP/1.1 in response
    
+
    Incorrect interpretation of HTTP/1.1 in response
    
 
 
    To quote from section 3.1 of RFC1945:
 
    
@@ -112,7 +112,7 @@ workaround is still:
 BrowserMatch "RealPlayer 4.0" force-response-1.0
 
    
 
-
    Requests use HTTP/1.1 but responses must be in HTTP/1.0
    
+
    Requests use HTTP/1.1 but responses must be in HTTP/1.0
    
 
 
    MSIE 4.0b2 has this problem.  Its Java VM makes requests in HTTP/1.1
 format but the responses must be in HTTP/1.0 format (in particular, it
@@ -125,7 +125,7 @@ This workaround is available in 1.2.2, and in a
 patch
  against 1.2.1.
 
-
    Boundary problems with header parsing
    
+
    Boundary problems with header parsing
    
 
 
    All versions of Navigator from 2.0 through 4.0b2 (and possibly later)
 have a problem if the trailing CRLF of the response header starts at
@@ -135,7 +135,7 @@ on all responses.  The workaround is to detect when this condition would
 occur in a response and add extra padding to the header to push the
 trailing CRLF past offset 258 of the response.
 
-
    Multipart responses and Quoted Boundary Strings
    
+
    Multipart responses and Quoted Boundary Strings
    
 
 
    On multipart responses some clients will not accept quotes (")
 around the boundary string.  The MIME standard recommends that
@@ -144,7 +144,7 @@ on one of the examples in RFC2068, which does not include quotes.
 Apache does not include quotes on its boundary strings to workaround
 this problem.
 
-
    Byterange requests
    
+
    Byterange requests
    
 
 
    A byterange request is used when the client wishes to retrieve a
 portion of an object, not necessarily the entire object.  There
@@ -185,7 +185,7 @@ with MSIE 3 is actually due to the Acrobat plugin, not due to the browser.
 version 3.01 is used with it, it will not properly understand byteranges.
 The user must upgrade their Acrobat reader to 3.01.
 
-
    Set-Cookie header is unmergeable
    
+
    Set-Cookie header is unmergeable
    
 
 
    The HTTP specifications say that it is legal to merge headers with
 duplicate names into one (separated by semicolon).  Some browsers
@@ -194,7 +194,7 @@ that support Cookies don't like merged headers and prefer that each
 headers returned by a CGI, Apache will explicitly avoid merging any
 Set-Cookie headers.
 
-
    Expires headers and GIF89A animations
    
+
    Expires headers and GIF89A animations
    
 
 
    Navigator versions 2 through 4 will erroneously re-request
 GIF89A animations on each loop of the animation if the first
@@ -205,7 +205,7 @@ HREF="http://www.arctic.org/~dgaudet/patches/apache-1.2-gif89-expires-hack.patch
 and for 1.3.
 
-
    POST without Content-Length
    
+
    POST without Content-Length
    
 
 
    In certain situations Navigator 3.01 through 3.03 appear to incorrectly
 issue a POST without the request body.  There is no
diff --git a/docs/manual/misc/perf-tuning.html b/docs/manual/misc/perf-tuning.html
index 33aab731a6..3d85d9df86 100644
--- a/docs/manual/misc/perf-tuning.html
+++ b/docs/manual/misc/perf-tuning.html
@@ -8,7 +8,7 @@
 
 
    Author: Dean Gaudet
 
-
    Introduction
    
+
    Introduction
    
 
    Apache is a general webserver, which is designed to be correct first, and
 fast second.  Even so, it's performance is quite satisfactory.  Most
 sites have less than 10Mbits of outgoing bandwidth, which Apache can
@@ -37,7 +37,7 @@ to Apache on NT.  Apache on NT has not been tuned for performance yet,
 in fact it probably performs very poorly because NT performance requires
 a different programming model.
 
-
    Hardware and Operating System Issues
    
+
    Hardware and Operating System Issues
    
 
 
    The single biggest hardware issue affecting webserver performance
 is RAM.  A webserver should never ever have to swap, swapping increases
@@ -57,9 +57,9 @@ HTTP serving completely breaks many of the assumptions built into Unix
 kernels up through 1994 and even 1995.  Good choices include
 recent FreeBSD, and Linux.
 
-
    Run-Time Configuration Issues
    
+
    Run-Time Configuration Issues
    
 
-
    HostnameLookups
    
+
    HostnameLookups
    
 
    Prior to Apache 1.3, HostnameLookups defaulted to On.
 This adds latency
 to every request because it requires a DNS lookup to complete before
@@ -88,7 +88,7 @@ But even still, if you just need DNS names
 in some CGIs you could consider doing the
 gethostbyname call in the specific CGIs that need it.
 
-
    FollowSymLinks and SymLinksIfOwnerMatch
    
+
    FollowSymLinks and SymLinksIfOwnerMatch
    
 
    Wherever in your URL-space you do not have an
 Options FollowSymLinks, or you do have an
 Options SymLinksIfOwnerMatch Apache will have to
@@ -126,7 +126,7 @@ document root.  For highest performance, and no symlink protection,
 set FollowSymLinks everywhere, and never set
 SymLinksIfOwnerMatch.
 
-
    AllowOverride
    
+
    AllowOverride
    
 
 
    Wherever in your URL-space you allow overrides (typically
 .htaccess files) Apache will attempt to open
@@ -146,7 +146,7 @@ The solutions are similar to the previous case of Options
 FollowSymLinks.  For highest performance use
 AllowOverride None everywhere in your filesystem.
 
-
    Negotiation
    
+
    Negotiation
    
 
 
    If at all possible, avoid content-negotiation if you're really
 interested in every last ounce of performance.  In practice the
@@ -166,7 +166,7 @@ DirectoryIndex index.cgi index.pl index.shtml index.html
 
 where you list the most common choice first.
 
-
    Process Creation
    
+
    Process Creation
    
 
 
    Prior to Apache 1.3 the MinSpareServers,
 MaxSpareServers, and StartServers settings
@@ -218,9 +218,9 @@ In no event should you raise this above about 60 seconds, as
 
 most of the benefits are lost.
 
-
    Compile-Time Configuration Issues
    
+
    Compile-Time Configuration Issues
    
 
-
    mod_status and Rule STATUS=yes
    
+
    mod_status and Rule STATUS=yes
    
 
 
    If you include mod_status
 and you also set Rule STATUS=yes when building
@@ -231,7 +231,7 @@ on your operating system), and (pre-1.3) several extra calls to
 contains timing indications.  For highest performance, set Rule
 STATUS=no.
 
-
    accept Serialization - multiple sockets
    
+
    accept Serialization - multiple sockets
    
 
 
    This discusses a shortcoming in the Unix socket API.
 Suppose your
@@ -390,7 +390,7 @@ low because highly parallel web servers are not the norm.
 
    Ideally you should run servers without multiple Listen
 statements if you want the highest performance.  But read on.
 
-
    accept Serialization - single socket
    
+
    accept Serialization - single socket
    
 
 
    The above is fine and dandy for multiple socket servers, but what
 about single socket servers?  In theory they shouldn't experience
@@ -418,7 +418,7 @@ and only an issue on LANs.  If you want to override the single socket
 serialization you can define SINGLE_LISTEN_UNSERIALIZED_ACCEPT
 and then single-socket servers will not serialize at all.
 
-
    Lingering Close
    
+
    Lingering Close
    
 
 
    As discussed in
 draft-ietf-http-connection-00.txt section 8,
@@ -484,7 +484,7 @@ is an absolute necessity (and
 pipelined connections are faster, so you
 want to support them).
 
-
    Scoreboard File
    
+
    Scoreboard File
    
 
 
    Apache's parent and children communicate with each other through
 something called the scoreboard.  Ideally this should be implemented
@@ -506,7 +506,7 @@ shared memory until version 1.2 of Apache.  This oversight resulted
 in really poor and unreliable behaviour of earlier versions of Apache
 on Linux.
 
-
    DYNAMIC_MODULE_LIMIT
    
+
    DYNAMIC_MODULE_LIMIT
    
 
 
    If you have no intention of using dynamically loaded modules
 (you probably don't if you're reading this and tuning your
@@ -515,7 +515,7 @@ server for every last ounce of performance) then you should add
 This will save RAM that's allocated only for supporting dynamically
 loaded modules.
 
-
    Appendix: Detailed Analysis of a Trace
    
+
    Appendix: Detailed Analysis of a Trace
    
 
 Here is a system call trace of Apache 1.3 running on Linux.  The run-time
 configuration file is essentially the default plus:
@@ -780,7 +780,7 @@ munmap(0x400e3000, 6144)                = 0
 That's 19 system calls, of which 4 remain relatively easy to remove,
 but don't seem worth the effort.
 
-
    Appendix: The Pre-Forking Model
    
+
    Appendix: The Pre-Forking Model
    
 
 
    Apache (on Unix) is a pre-forking model server.  The
 parent process is responsible only for forking child
diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html
index 132aa347d2..c4e74b594b 100644
--- a/docs/manual/mod/core.html
+++ b/docs/manual/mod/core.html
@@ -1791,7 +1791,7 @@ sets the SERVER_PORT environment variable (for
 and is used when the server must generate a URL that refers to itself
 (for example when creating an external redirect to itself).  This
 behaviour is modified by
-UseCanonicalName.
+UseCanonicalName.
 
 
 In no event does a Port setting affect
@@ -1802,7 +1802,7 @@ The primary behaviour of Port should be considered to be similar to that of
 the ServerName directive.  The ServerName
 and Port together specify what you consider to be the canonical
 address of the server.
-(See also UseCanonicalName.)
    
+(See also UseCanonicalName.)
    
 
 Port 80 is one of Unix's special ports. All ports numbered
 below 1024 are reserved for system use, i.e. regular (non-root) users cannot
@@ -2190,9 +2190,9 @@ not work reliably, or may not return the preferred hostname. For example:
 
    ServerName www.wibble.com
    
 would be used if the canonical (main) name of the actual machine
 were monster.wibble.com.
    
-
    See Also:
    
-DNS Issues
    
-UseCanonicalName
    
+
    See Also:
    
+DNS Issues
    
+UseCanonicalName
    
 
    
 
    
 
@@ -2452,45 +2452,45 @@ a packet is sent.
 
 Compatibility: UseCanonicalName is only available in Apache 1.3 and later
    
 
-In many situations Apache has to construct a self-referential
+In many situations Apache has to construct a self-referential
 URL.  That is, a URL which refers back to the same server.
-With UseCanonicalName on (and in all versions prior to
-1.3) Apache will use the ServerName and Port directives to construct a canonical name for the
+With UseCanonicalName on (and in all versions prior to
+1.3) Apache will use the ServerName and Port directives to construct a canonical name for the
 server.  This name is used in all self-referential URLs, and for the
-values of SERVER_NAME and SERVER_PORT in CGIs.
+values of SERVER_NAME and SERVER_PORT in CGIs.
 
-
    With UseCanonicalName off Apache will form
+
    With UseCanonicalName off Apache will form
 self-referential URLs using the hostname and port supplied
 by the client if any are supplied (otherwise it will use the
 canonical name).  These values are the same that are used to
-implement name based virtual
-hosts, and are available with the same clients.  The CGI variables
-SERVER_NAME and SERVER_PORT will be constructed
+implement name based virtual
+hosts, and are available with the same clients.  The CGI variables
+SERVER_NAME and SERVER_PORT will be constructed
 from the client supplied values as well.
 
-
    An example where this may be useful is on an intranet server where
+
    An example where this may be useful is on an intranet server where
 you have users connecting to the machine using short names such as
-www.  You'll notice that if the users type a shortname,
-and a URL which is a directory, such as http://www/splat,
-without the trailing slash then Apache will redirect them to
-http://www.domain.com/splat/.  If you have authentication
+www.  You'll notice that if the users type a shortname,
+and a URL which is a directory, such as http://www/splat,
+without the trailing slash then Apache will redirect them to
+http://www.domain.com/splat/.  If you have authentication
 enabled, this will cause the user to have to reauthenticate twice (once
-for www and once again for www.domain.com).
-But if UseCanonicalName is set off, then Apache will redirect
-to http://www/splat/.
+for www and once again for www.domain.com).
+But if UseCanonicalName is set off, then Apache will redirect
+to http://www/splat/.
 
-
    Warning: if CGIs make assumptions about the values of
-SERVER_NAME they may be broken by this option.  The client
+
    Warning: if CGIs make assumptions about the values of
+SERVER_NAME they may be broken by this option.  The client
 is essentially free to give whatever value they want as a hostname.
-But if the CGI is only using SERVER_NAME to construct
+But if the CGI is only using SERVER_NAME to construct
 self-referential URLs then it should be just fine.
 
-
    See also:
-ServerName,
-Port
+
    See also:
+ServerName,
+Port
 
-
    
+
    
 
 
    User directive
    
 
diff --git a/docs/manual/mod/mod_access.html b/docs/manual/mod/mod_access.html
index b3ffda53fa..c004dd1936 100644
--- a/docs/manual/mod/mod_access.html
+++ b/docs/manual/mod/mod_access.html
@@ -31,7 +31,7 @@ hostname or IP address.
 
    
 
 
-
    allow directive
    
+
    allow directive
    
 
    
 
 order.
 
    
 
    
 
-
    deny directive
    
+
    deny directive
    
 
    
 
 order.
 
    
 
    
 
-
    order directive
    
+
    order directive
    
 
    
 
 
-
    Summary
    
+
    Summary
    
 
    
 This module lets you run CGI scripts whenever a file of a certain type
 is requested. This makes it much easier to execute scripts that
 process files.
 
    
-
    Directives
    
+
    Directives
    
 
    • 
 
 
    
-
    Directives
    
+
    Directives
    
     
 
    
 
 
-
    XBitHack
    
+
    XBitHack
    
 
 
 
 
    
-
    Using Server Side Includes for ErrorDocuments
    
+
    Using Server Side Includes for ErrorDocuments
    
 
 There is     a document which
 describes how to use the features of mod_include to offer internationalized
diff --git a/docs/manual/mod/mod_info.html b/docs/manual/mod/mod_info.html
index 306bc8663c..8afa84dc41 100644
--- a/docs/manual/mod/mod_info.html
+++ b/docs/manual/mod/mod_info.html
@@ -13,7 +13,7 @@
  ALINK="#FF0000"
 >
 
-
    Module mod_info
    
+
    Module mod_info
    
 
 This module is contained in the mod_info.c file.  It
 provides a comprehensive overview of the server configuration
diff --git a/docs/manual/mod/mod_isapi.html b/docs/manual/mod/mod_isapi.html
index a8e3233932..bb7426379d 100644
--- a/docs/manual/mod/mod_isapi.html
+++ b/docs/manual/mod/mod_isapi.html
@@ -21,14 +21,14 @@
    running under Microsoft Windows. Any document with a handler of
    isapi-isa will be processed by this module.
 
-
    Purpose
    
+
    Purpose
    
 
 
    This module implements the ISAPI
    Extension API. It allows Internet Server Applications (i.e., ISAPI
    Extensions) to be used with Apache for Windows.
 
-
    Usage
    
+
    Usage
    
 
 
    In the server configuration file, add a handler called
    isapi-isa, and map it to files with a .DLL
@@ -43,7 +43,7 @@
    scripts. That is, Options ExecCGI must be active in the
    directory that contains the ISA.
    
 
-
    Notes
    
+
    Notes
    
 
 
    Apache's ISAPI implementation conforms to all of the ISAPI 2.0
    specification, except for the "Microsoft-specific" extensions dealing
diff --git a/docs/manual/mod/mod_log_agent.html b/docs/manual/mod/mod_log_agent.html
index 43252dd4a2..5f1483f7d7 100644
--- a/docs/manual/mod/mod_log_agent.html
+++ b/docs/manual/mod/mod_log_agent.html
@@ -25,7 +25,7 @@ compiled in by default. It provides for logging of the client user agents.
 
    
 
 
-
    AgentLog
    
+
    AgentLog
    
 
 Summary
+
    Summary
    
 
 Three directives are provided by this module: TransferLog
 to create a log file, LogFormat to set a custom format,
@@ -31,7 +31,7 @@ be used multiple times in each server to cause each request to be
 logged to multiple files.
 
    
 
-
    Compatibility notes
    
+
    Compatibility notes
    
 
 
      
 
    • This module is based on mod_log_config distributed with
@@ -47,7 +47,7 @@ should be defined to log user-tracking information instead.
 
 
    
 
-
    Log File Formats
    
+
    Log File Formats
    
 
 Unless told otherwise with LogFormat the log files created by
 TransferLog will be in standard "Common Log Format"
@@ -56,7 +56,7 @@ below. Alternatively, the log file can be customized (and if multiple
 log files are used, each can have a different format). Custom formats
 are set with LogFormat and CustomLog.
 
-
    Common Log Format
    
+
    Common Log Format
    
 
 The Common Log Format (CLF) file contains a separate line for each
 request. A line is composed of several tokens separated by spaces:
@@ -97,7 +97,7 @@ zone = (`+' | `-') 4*digit
    • any headers.
    -

    Custom Log Formats

    +

    Custom Log Formats

    The format argument to the LogFormat and CustomLog is a string. This string is logged to the log @@ -153,14 +153,14 @@ Note that the common log format is defined by the string "%h %l extending for format if desired (e.g. to add extra fields at the end). NCSA's extended/combined log format would be "%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-agent}i\"". -

    Using Multiple Log Files

    +

    Using Multiple Log Files

    The TransferLog and CustomLog directives can be given more than once to log requests to multiple log files. Each request will be logged to all the log files defined by either of these directives. -

    Use with Virtual Hosts

    +

    Use with Virtual Hosts

    If a <VirtualHost> section does not contain any TransferLog or CustomLog directives, the @@ -171,14 +171,14 @@ within its definition, not in any of the main server's log files. See the examples below.

    -

    Security Considerations

    +

    Security Considerations

    See the security tips document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.

    -

    Directives

    +

    Directives