From: Ken Coar Date: Thu, 5 Feb 1998 21:20:02 +0000 (+0000) Subject: Correcting some HTML boo-boos (not subject to style debates). X-Git-Tag: APACHE_1_3b5~8 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6241994012d47ce3b6aece04b56b53a9c7ffdb52;p=thirdparty%2Fapache%2Fhttpd.git Correcting some HTML boo-boos (not subject to style debates). It has been said, and verily it is true, that weblint rocks. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@80132 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/custom_errordocs.html b/docs/manual/misc/custom_errordocs.html index 93b144c32d7..261f1b86beb 100644 --- a/docs/manual/misc/custom_errordocs.html +++ b/docs/manual/misc/custom_errordocs.html @@ -12,9 +12,7 @@ VLINK="#000080" ALINK="#FF0000" > -
- [APACHE DOCUMENTATION] -
+

Using XSSI and ErrorDocument to configure customized international server error responses

@@ -30,7 +28,7 @@ customized international server error responses
  • HTML listing of the discussed example
    -

    Introduction

     +

    Introduction

    This document describes an easy way to provide your apache WWW server with a set of customized error messages which take advantage of Content Negotiation @@ -76,14 +74,15 @@ For this hypothetic server, we assume that all error messages...

    An example of a "document not found" message for a german client might look like this:
    -
    +[Needs graphics capability to display]
    All links in the document as well as links to the server's administrator mail address, and even the name and port of the serving virtual host are inserted in the error document at "run-time", i.e., when the error actually occurs.

    -

    Creating an ErrorDocument directory

     +

    Creating an ErrorDocument directory

    For this concept to work as easily as possible, we must take advantage of as much server support as we can get: @@ -159,7 +158,7 @@ The directory for the error messages (here: appropriate permissions (readable and executable by the server uid or gid, only writable for the administrator). -

    Naming the individual error document files

     +

    Naming the individual error document files

    By defining the MultiViews option, the server was told to automatically scan the directory for matching variants (looking at language @@ -186,7 +185,7 @@ the configured error documents): variant (see below). -

    The common header and footer files

     +

    The common header and footer files

    By putting as much layout information in two special "include files", the error documents can be reduced to a bare minimum. @@ -229,7 +228,7 @@ See the listings below to see an actual HTML implementation of the discussed example. -

    Creating ErrorDocuments in different languages

     +

    Creating ErrorDocuments in different languages

    After all this preparation work, little remains to be said about the actual documents. They all share a simple common structure: @@ -243,7 +242,7 @@ In the listings section, you can see an example of a [400 Bad Request] error document. Documents as simple as that certainly cause no problems to translate or expand. -

    The fallback language

     +

    The fallback language

    Do we need a special handling for languages other than those we have translations for? We did set the LanguagePriority, didn't we?! @@ -276,7 +275,7 @@ A simple shell script to do it (execute within the errordocs/ dir):

    -

    HTML listing of the discussed example

     +

    HTML listing of the discussed example

    So, to summarize our example, here's the complete listing of the 400.shtml.en document. You will notice that it contains diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html index cb102b41031..e06b4f10fef 100644 --- a/docs/manual/misc/known_client_problems.html +++ b/docs/manual/misc/known_client_problems.html @@ -40,7 +40,7 @@ The admin typically controls which are set, and for which clients, by using mod_browser. Unless otherwise noted all of these workarounds exist in versions 1.2 and later. -

    Trailing CRLF on POSTs

     +

    Trailing CRLF on POSTs

    This is a legacy issue. The CERN webserver required POST data to have an extra CRLF following it. Thus many @@ -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,11 +72,11 @@ 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:

    -HTTP uses a "." numbering scheme to indicate versions +HTTP uses a "<MAJOR>.<MINOR>" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather than the features @@ -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 3d85d9df864..19d5effd814 100644 --- a/docs/manual/misc/perf-tuning.html +++ b/docs/manual/misc/perf-tuning.html @@ -327,8 +327,8 @@ the inner loop. The loop looks like this (differences highlighted): } - -The functions accept_mutex_on and accept_mutex_off +The functions +accept_mutex_on and accept_mutex_off implement a mutual exclusion semaphore. Only one child can have the mutex at any time. There are several choices for implementing these mutexes. The choice is defined in src/conf.h (pre-1.3) or diff --git a/docs/manual/misc/security_tips.html b/docs/manual/misc/security_tips.html index d454122ebc8..ce261b132c8 100644 --- a/docs/manual/misc/security_tips.html +++ b/docs/manual/misc/security_tips.html @@ -22,8 +22,7 @@ the suggestions will be general, others specific to Apache.

    - -

    Permissions on ServerRoot Directories

     +

    Permissions on ServerRoot Directories

    In typical operation, Apache is started by the root user, and it switches to the user defined by the User directive to serve hits. diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index 2a4e25cec1c..4856f4c55bd 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -80,12 +80,10 @@ gifted exclusively to the The Apache Group in July 1997 by

    - -

    Configuration Directives

    -     +

    Configuration Directives

    -

    RewriteEngine

     +

    RewriteEngine

    RewriteOptions inherit is enabled.

    -

    RewriteOptions

    +

    RewriteOptions

    -

    RewriteLog

    +

    RewriteLog

    -

    RewriteLogLevel

    +

    RewriteLogLevel

    -

    RewriteMap

    +

    RewriteMap

    -The Mapname is the name of the map and will +The Mapname is the name of the map and will be used to specify a mapping-function for the substitution strings of a rewriting rule via @@ -405,7 +403,7 @@ only happens once!

    -

    RewriteBase

    +

    RewriteBase

    -

    RewriteCond

    +

    RewriteCond

    $N -(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the +(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) +of the pattern from the corresponding RewriteRule directive (the one following the current bunch of RewriteCond directives). @@ -561,7 +560,7 @@ following the current bunch of RewriteCond directives). %N -(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the +(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the pattern from the last matched RewriteCond directive in the current bunch of conditions. @@ -822,7 +821,7 @@ use any other browser you get the standard homepage.

    -

    RewriteRule

    +

    RewriteRule

    definition order of these rules is run-time.

    -Pattern can be (for Apache 1.1.x a System -V8 and for Apache 1.2.x a POSIX) regular expression +Pattern can be (for Apache 1.1.x a System +V8 and for Apache 1.2.x a POSIX) regular expression which gets applied to the current URL. Here ``current'' means the value of the URL when this rule gets applied. This may not be the original requested URL, because there could be any number of rules before which already matched @@ -897,7 +896,7 @@ substitution string!

    -Substitution of a rewriting rule is the string +Substitution of a rewriting rule is the string which is substituted for (or replaces) the original URL for which Pattern matched. Beside plain text you can use @@ -966,7 +965,7 @@ as the third argument to the RewriteRule directive. Flags is a comma-separated list of the following flags: