From ed488c48e5b6cb869fe26e7388f0e74876f7455b Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Sat, 9 Sep 2000 18:19:55 +0000 Subject: [PATCH] PR: 6470,6450,6218,6216,6478 Submitted by: pepper@reppep.com Reviewed by: Joshua Slive Grammar fixes from the bug database. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86189 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/FAQ-H.html | 26 ++++++++++++++------------ docs/manual/misc/perf-tuning.html | 12 ++++++------ docs/manual/mod/core.html | 2 +- docs/manual/mod/mod_alias.html | 2 +- docs/manual/vhosts/name-based.html | 2 +- docs/manual/vhosts/name-based.html.en | 2 +- 6 files changed, 24 insertions(+), 22 deletions(-) diff --git a/docs/manual/misc/FAQ-H.html b/docs/manual/misc/FAQ-H.html index 3369ec9c3d..778884c74d 100644 --- a/docs/manual/misc/FAQ-H.html +++ b/docs/manual/misc/FAQ-H.html @@ -31,7 +31,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.1 $ ($Date: 1999/06/24 15:02:52 $) + $Revision: 1.2 $ ($Date: 2000/09/09 18:19:54 $)

The latest version of this FAQ is always available from the main @@ -211,19 +211,21 @@

- You can't! The reason is: First, case translations for arbitrary - length URLs cannot be done via regex patterns and - corresponding substitutions. One need a per-character pattern like - sed/Perl tr|..|..| feature. Second, just making URLs - always upper or lower case will not resolve the complete problem of - case-INSENSITIVE URLs, because actually the URLs had to be rewritten - to the correct case-variant residing on the filesystem because in - later processing Apache needs to access the file. And Unix - filesystem is always case-SENSITIVE. + You can't! The reasons are: first, that, case translations for + arbitrary length URLs cannot be done via regex patterns and + corresponding substitutions. One needs a per-character pattern like + the sed/Perl tr|..|..| feature. Second, just making + URLs always upper or lower case does not solve the whole problem of + case-INSENSITIVE URLs, because URLs actually have to be rewritten to + the correct case-variant for the file residing on the filesystem + in order to allow Apache to access the file. And + the Unix filesystem is always case-SENSITIVE.

- But there is a module named mod_speling.c (yes, it is named - this way!) out there on the net. Try this one. + But there is a module named mod_speling.c in the + Apache distribution. Try this module to help correct people who use + mis-cased URLs.

diff --git a/docs/manual/misc/perf-tuning.html b/docs/manual/misc/perf-tuning.html index b32ad7c92f..c9c1348c80 100644 --- a/docs/manual/misc/perf-tuning.html +++ b/docs/manual/misc/perf-tuning.html @@ -359,7 +359,7 @@ mutex. Unfortunately SysV-style semaphores have some bad side-effects. One is that it's possible Apache will die without cleaning up the semaphore (see the ipcs(8) man page). The other is that the semaphore API allows for a denial of service attack by any CGIs running under the -same uid as the webserver (i.e., all CGIs unless you use something +same uid as the webserver (i.e., all CGIs, unless you use something like suexec or cgiwrapper). For these reasons this method is not used on any architecture except IRIX (where the previous two are prohibitively expensive on most IRIX boxes). @@ -446,7 +446,7 @@ The TCP specification does not state that the FIN_WAIT_2 state has a timeout, but it doesn't prohibit it. On systems without the timeout, Apache 1.2 induces many sockets stuck forever in the FIN_WAIT_2 state. In many cases this can be avoided by simply upgrading to the latest -TCP/IP patches supplied by the vendor, in cases where the vendor has +TCP/IP patches supplied by the vendor. In cases where the vendor has never released patches (i.e., SunOS4 -- although folks with a source license can patch it themselves) we have decided to disable this feature. @@ -799,8 +799,8 @@ but don't seem worth the effort. There are -several performance patches available for 1.3. But they may -be slightly out of date by the time Apache 1.3.0 has been released, +several performance patches available for 1.3. Although they may +not apply cleanly to the current version, it shouldn't be difficult for someone with a little C knowledge to update them. In particular: @@ -856,8 +856,8 @@ depending on the operating system.

Apache's core code is already multithread aware, and Apache version 1.3 is multithreaded on NT. There have been at least two other experimental implementations of threaded Apache, one using the 1.3 code base on DCE, -and one using a custom user-level threads package and the 1.0 code base, -neither are available publically. There is also an experimental port of +and one using a custom user-level threads package and the 1.0 code base; +neither is available publically. There is also an experimental port of Apache 1.3 to Netscape's Portable Run Time, which is available diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 78d4b610d2..3588077c92 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -3393,7 +3393,7 @@ TransferLog logs/host.foo.com-access_log
Each VirtualHost must correspond to a different IP address, different port number or a -different host name for the server, in the latter case the server +different host name for the server, in the former case the server machine must be configured to accept IP packets for multiple addresses. (If the machine does not have multiple network interfaces, then this can be accomplished with the ifconfig alias diff --git a/docs/manual/mod/mod_alias.html b/docs/manual/mod/mod_alias.html index 0826842cde..1295bd9e6d 100644 --- a/docs/manual/mod/mod_alias.html +++ b/docs/manual/mod/mod_alias.html @@ -183,7 +183,7 @@ when used with .htaccess files or inside of <Directory> sections.

If no status argument is given, the redirect will be "temporary" (HTTP status 302). This indicates to the client that the -resources is has moved temporarily. The status +resource has moved temporarily. The status argument can be used to return other HTTP status codes:

diff --git a/docs/manual/vhosts/name-based.html b/docs/manual/vhosts/name-based.html index 238cf5c721..ac5a8d063f 100644 --- a/docs/manual/vhosts/name-based.html +++ b/docs/manual/vhosts/name-based.html @@ -78,7 +78,7 @@ are pointing to the IP address 111.22.33.44

directive then requests to that IP address will only ever be served by matching <VirtualHost>s. The "main server" will never be served from the specified IP address. -If you start to use virtual hosts you should stop to use the "main server" +If you start to use virtual hosts you should stop using the "main server" as an independent server and rather use it as a place for configuration directives that are common for all your virtual hosts. In other words, you should add a <VirtualHost> section for diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en index 238cf5c721..ac5a8d063f 100644 --- a/docs/manual/vhosts/name-based.html.en +++ b/docs/manual/vhosts/name-based.html.en @@ -78,7 +78,7 @@ are pointing to the IP address 111.22.33.44

directive then requests to that IP address will only ever be served by matching <VirtualHost>s. The "main server" will never be served from the specified IP address. -If you start to use virtual hosts you should stop to use the "main server" +If you start to use virtual hosts you should stop using the "main server" as an independent server and rather use it as a place for configuration directives that are common for all your virtual hosts. In other words, you should add a <VirtualHost> section for -- 2.50.1