httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_dll.html mod_rewrite.html mod_speling.html
Date Thu, 05 Feb 1998 21:20:03 GMT
coar        98/02/05 13:20:03

  Modified:    htdocs/manual windows.html
               htdocs/manual/misc custom_errordocs.html
                        known_client_problems.html perf-hp.html
                        perf-tuning.html security_tips.html
               htdocs/manual/mod mod_dll.html mod_rewrite.html
  	Correcting some HTML boo-boos (not subject to style debates).
  	It has been said, and verily it is true, that weblint rocks.
  Revision  Changes    Path
  1.11      +3 -3      apache-1.3/htdocs/manual/windows.html
  Index: windows.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- windows.html	1998/02/05 20:04:16	1.10
  +++ windows.html	1998/02/05 21:19:54	1.11
  @@ -118,7 +118,7 @@
      directory, on the current hard drive. Another directory may be used,
      but the files will need to be installed manually.</P>
  -<P>To install the files into the </CODE>\Apache</CODE> directory
  +<P>To install the files into the <CODE>\Apache</CODE> directory
      automatically, use one the following nmake commands (see above):</P>
   <LI><CODE>nmake /f Makefile.nt installr</CODE> (for release build)
  @@ -211,13 +211,13 @@
      line, or as a Windows NT service. To run it from the command line, use
      the following command:
  -    C:\Apache> <STRONG>apache -s</STRONG>
  +    C:\Apache&gt; <STRONG>apache -s</STRONG>
   <P>Apache will then execute, and will remain running until it is
      exited. To use Apache as a Windows NT service, use the following:</P>
  -    C:\Apache> <STRONG>apache -i</STRONG>
  +    C:\Apache&gt; <STRONG>apache -i</STRONG>
   <P>Then open the Services control panel, and start the Apache service.</P>
  1.3       +10 -11    apache-1.3/htdocs/manual/misc/custom_errordocs.html
  Index: custom_errordocs.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/custom_errordocs.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- custom_errordocs.html	1998/02/05 20:04:28	1.2
  +++ custom_errordocs.html	1998/02/05 21:19:56	1.3
  @@ -12,9 +12,7 @@
  - <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]">
  +<!--#include virtual="header.html" -->
   <H1 ALIGN="CENTER">Using XSSI and <SAMP>ErrorDocument</SAMP> to configure
   customized international server error responses</H1>
  @@ -30,7 +28,7 @@
    <LI><A HREF="#listings">HTML listing of the discussed example</A>
  -<A NAME="intro"><H2>Introduction</H2></A>
  +<H2><A NAME="intro">Introduction</A></H2>
   This document describes an easy way to provide your apache WWW server
   with a set of customized error messages which take advantage of
   <A HREF="../content-negotiation.html">Content Negotiation</A>
  @@ -76,14 +74,15 @@
   An example of a "document not found" message for a german client might
   look like this:<BR>
  -<IMG SRC="../images/custom_errordocs.gif"><BR>
  +<IMG SRC="../images/custom_errordocs.gif"
  + ALT="[Needs graphics capability to display]"><BR>
   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.
  -<A NAME="createdir"><H2>Creating an ErrorDocument directory</H2></A>
  +<H2><A NAME="createdir">Creating an ErrorDocument directory</A></H2>
   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 @@
   appropriate permissions (readable and executable by the server uid or gid, 
   only writable for the administrator).
  -<A NAME="docnames"><H3>Naming the individual error document files</H3></A>
  +<H3><A NAME="docnames">Naming the individual error document files</A></H3>
   By defining the <SAMP>MultiViews</SAMP> option, the server was told to
   automatically scan the directory for matching variants (looking at language
  @@ -186,7 +185,7 @@
        variant (<A HREF="#fallback">see below</A>).
  -<A NAME="headfoot"><H3>The common header and footer files</H3></A>
  +<H3><A NAME="headfoot">The common header and footer files</A></H3>
   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 @@
   implementation of the discussed example.
  -<A NAME="createdocs"><H3>Creating ErrorDocuments in different languages</H3></A>
  +<H3><A NAME="createdocs">Creating ErrorDocuments in different languages</A></H3>
   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 @@
   of a [400 Bad Request] error document. Documents as simple as that
   certainly cause no problems to translate or expand.
  -<A NAME="fallback"><H3>The fallback language</H3></A>
  +<H3><A NAME="fallback">The fallback language</A></H3>
   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 NAME="listings"><H2>HTML listing of the discussed example</H2></A>
  +<H2><A NAME="listings">HTML listing of the discussed example</A></H2>
   So, to summarize our example, here's the complete listing of the
   <SAMP>400.shtml.en</SAMP> document. You will notice that it contains
  1.9       +11 -11    apache-1.3/htdocs/manual/misc/known_client_problems.html
  Index: known_client_problems.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/known_client_problems.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- known_client_problems.html	1998/02/05 20:04:29	1.8
  +++ known_client_problems.html	1998/02/05 21:19:56	1.9
  @@ -40,7 +40,7 @@
   <A HREF="../mod/mod_browser.html">mod_browser</A>.  Unless otherwise
   noted all of these workarounds exist in versions 1.2 and later.
  -<A name="trailing-crlf"><H3>Trailing CRLF on POSTs</H3></A>
  +<H3><A name="trailing-crlf">Trailing CRLF on POSTs</A></H3>
   <P>This is a legacy issue.  The CERN webserver required <CODE>POST</CODE>
   data to have an extra <CODE>CRLF</CODE> following it.  Thus many
  @@ -49,7 +49,7 @@
   Apache works around this problem by eating any empty lines which
   appear before a request.
  -<A name="broken-keepalive"><H3>Broken keepalive</H3></A>
  +<H3><A name="broken-keepalive">Broken keepalive</A></H3>
   <P>Various clients have had broken implementations of <EM>keepalive</EM>
   (persistent connections).  In particular the Windows versions of
  @@ -72,11 +72,11 @@
   BrowserMatch "MSIE 4\.0b2;" nokeepalive
  -<A name="force-response-1.0"><H3>Incorrect interpretation of <CODE>HTTP/1.1</CODE>
in response</H3></A>
  +<H3><A name="force-response-1.0">Incorrect interpretation of <CODE>HTTP/1.1</CODE>
in response</A></H3>
   <P>To quote from section 3.1 of RFC1945:
  -HTTP uses a "<MAJOR>.<MINOR>" numbering scheme to indicate versions
  +HTTP uses a "&lt;MAJOR&gt;.&lt;MINOR&gt;" numbering scheme to indicate
   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 @@
   BrowserMatch "RealPlayer 4.0" force-response-1.0
  -<A name="msie4.0b2"><H3>Requests use HTTP/1.1 but responses must be in HTTP/1.0</H3></A>
  +<H3><A name="msie4.0b2">Requests use HTTP/1.1 but responses must be in HTTP/1.0</A></H3>
   <P>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 @@
   <A HREF="">patch
   </A> against 1.2.1.
  -<A name="257th-byte"><H3>Boundary problems with header parsing</H3></A>
  +<H3><A name="257th-byte">Boundary problems with header parsing</A></H3>
   <P>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 @@
   occur in a response and add extra padding to the header to push the
   trailing CRLF past offset 258 of the response.
  -<A name="boundary-string"><H3>Multipart responses and Quoted Boundary Strings</H3></A>
  +<H3><A name="boundary-string">Multipart responses and Quoted Boundary Strings</A></H3>
   <P>On multipart responses some clients will not accept quotes (")
   around the boundary string.  The MIME standard recommends that
  @@ -144,7 +144,7 @@
   Apache does not include quotes on its boundary strings to workaround
   this problem.
  -<A name="byterange-requests"><H3>Byterange requests</H3></A>
  +<H3><A name="byterange-requests">Byterange requests</A></H3>
   <P>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 @@
   version 3.01 is used with it, it will not properly understand byteranges.
   The user must upgrade their Acrobat reader to 3.01.
  -<A name="cookie-merge"><H3><CODE>Set-Cookie</CODE> header is unmergeable</H3></A>
  +<H3><A name="cookie-merge"><CODE>Set-Cookie</CODE> header is unmergeable</A></H3>
   <P>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 @@
   headers returned by a CGI, Apache will explicitly avoid merging any
   <CODE>Set-Cookie</CODE> headers.
  -<A name="gif89-expires"><H3><CODE>Expires</CODE> headers and GIF89A
  +<H3><A name="gif89-expires"><CODE>Expires</CODE> headers and GIF89A
   <P>Navigator versions 2 through 4 will erroneously re-request
   GIF89A animations on each loop of the animation if the first
  @@ -205,7 +205,7 @@
   and for <A
  -<A name="no-content-length"><H3><CODE>POST</CODE> without <CODE>Content-Length</CODE></H3></A>
  +<H3><A name="no-content-length"><CODE>POST</CODE> without <CODE>Content-Length</CODE></A></H3>
   <P>In certain situations Navigator 3.01 through 3.03 appear to incorrectly
   issue a POST without the request body.  There is no
  1.4       +3 -9      apache-1.3/htdocs/manual/misc/perf-hp.html
  Index: perf-hp.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/perf-hp.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- perf-hp.html	1998/01/26 16:53:55	1.3
  +++ perf-hp.html	1998/02/05 21:19:57	1.4
  @@ -12,15 +12,9 @@
  -<A NAME="initial">
  - <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]">
  - <H3>
  -  Apache HTTP Server Version 1.3
  - </H3>
  +<A NAME="initial">&nbsp;</A>
  +<!--#include virtual="header.html" -->
   <H1 ALIGN="CENTER">Running a High-Performance Web Server for HPUX</H1>
  @@ -73,7 +67,7 @@
   If folks are running Apache on a PA-8000 based system, they should
   consider "chatr'ing" the Apache executable to have a large page size.
  -This would be "chatr +pi L <BINARY>." The GID of the running executable
  +This would be "chatr +pi L &lt;BINARY&gt;." The GID of the running executable
   must have MLOCK privileges. Setprivgrp(1m) should be consulted for
   assigning MLOCK. The change can be validated by running Glance and
   examining the memory regions of the server(s) to make sure that they
  1.8       +2 -2      apache-1.3/htdocs/manual/misc/perf-tuning.html
  Index: perf-tuning.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/perf-tuning.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- perf-tuning.html	1998/02/05 20:04:30	1.7
  +++ perf-tuning.html	1998/02/05 21:19:57	1.8
  @@ -327,8 +327,8 @@
  -<A name="serialize"></A>
  -The functions <CODE>accept_mutex_on</CODE> and <CODE>accept_mutex_off</CODE>
  +<A name="serialize">The functions</A>
  +<CODE>accept_mutex_on</CODE> and <CODE>accept_mutex_off</CODE>
   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 <CODE>src/conf.h</CODE> (pre-1.3) or
  1.14      +1 -2      apache-1.3/htdocs/manual/misc/security_tips.html
  Index: security_tips.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/security_tips.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- security_tips.html	1998/01/26 16:53:56	1.13
  +++ security_tips.html	1998/02/05 21:19:58	1.14
  @@ -22,8 +22,7 @@
  -<A name="serverroot">
  -<H2>Permissions on ServerRoot Directories</H2></A>
  +<H2><A name="serverroot">Permissions on ServerRoot Directories</A></H2>
   <P>In typical operation, Apache is started by the root
   user, and it switches to the user defined by the <A
   HREF="../mod/core.html#user"><STRONG>User</STRONG></A> directive to
serve hits.
  1.7       +1 -1      apache-1.3/htdocs/manual/mod/mod_dll.html
  Index: mod_dll.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_dll.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- mod_dll.html	1998/02/05 20:04:46	1.6
  +++ mod_dll.html	1998/02/05 21:20:00	1.7
  @@ -14,7 +14,7 @@
   <!--#include virtual="header.html" -->
   <H1 ALIGN="CENTER">Module mod_dll</H1>
   This module is contained in the <CODE>mod_dll.c</CODE> file, and is 
   compiled in by default for Windows. It provides for loading of executable code
   and modules into the server at start-up time, when they are contained in
  1.22      +19 -24    apache-1.3/htdocs/manual/mod/mod_rewrite.html
  Index: mod_rewrite.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_rewrite.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- mod_rewrite.html	1998/02/05 20:04:58	1.21
  +++ mod_rewrite.html	1998/02/05 21:20:01	1.22
  @@ -80,12 +80,10 @@
  -<A name="Configuration">
  -<H1>Configuration Directives</H1>
  +<H1><A NAME="Configuration">Configuration Directives</A></H1>
  -<A name="RewriteEngine"><H3>RewriteEngine</H3></A>
  +<H3><A NAME="RewriteEngine">RewriteEngine</A></H3>
  @@ -119,7 +117,7 @@
   <hr noshade size=1>
  -<A name="RewriteOptions"><H3>RewriteOptions</H3></A>
  +<H3><A NAME="RewriteOptions">RewriteOptions</A></H3>
  @@ -151,7 +149,7 @@
   <hr noshade size=1>
  -<A name="RewriteLog"><H3>RewriteLog</H3></A>
  +<H3><A NAME="RewriteLog">RewriteLog</A></H3>
  @@ -209,7 +207,7 @@
   <hr noshade size=1>
  -<A name="RewriteLogLevel"><H3>RewriteLogLevel</H3></A>
  +<H3><A NAME="RewriteLogLevel">RewriteLogLevel</A></H3>
  @@ -254,7 +252,7 @@
   <hr noshade size=1>
  -<A name="RewriteMap"><H3>RewriteMap</H3></A>
  +<H3><A NAME="RewriteMap">RewriteMap</A></H3>
  @@ -274,7 +272,7 @@
   to insert/substitute fields through a key lookup.
  -The <A name="mapfunc"><EM>Mapname</EM></A> is the name of the map
and will
  +The <A NAME="mapfunc"><EM>Mapname</EM></A> 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 @@
   <hr noshade size=1>
  -<A name="RewriteBase"><H3>RewriteBase</H3></A>
  +<H3><A NAME="RewriteBase">RewriteBase</A></H3>
  @@ -517,7 +515,7 @@
   <hr noshade size=1>
  -<A name="RewriteCond"><H3>RewriteCond</H3></A>
  +<H3><A NAME="RewriteCond">RewriteCond</A></H3>
  @@ -550,7 +548,8 @@
  -(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the
  +(1 &lt;= N &lt;= 9) which provide access to the grouped parts (parenthesis!)
  +of the
   pattern from the corresponding <TT>RewriteRule</TT> directive (the one
   following the current bunch of <TT>RewriteCond</TT> directives).
  @@ -561,7 +560,7 @@
  -(1 <= N <= 9) which provide access to the grouped parts (parenthesis!) of the
  +(1 &lt;= N &lt;= 9) which provide access to the grouped parts (parenthesis!) of
   pattern from the last matched <TT>RewriteCond</TT> directive in the current
   bunch of conditions.
  @@ -822,7 +821,7 @@
   <hr noshade size=1>
  -<A name="RewriteRule"><H3>RewriteRule</H3></A>
  +<H3><A NAME="RewriteRule">RewriteRule</A></H3>
  @@ -844,8 +843,8 @@
  -<A name="patterns"><EM>Pattern</EM></A> can be (for Apache 1.1.x
a System
  -V8 and for Apache 1.2.x a POSIX) <A name="regexp">regular expression</A>
  +<A NAME="patterns"><EM>Pattern</EM></A> can be (for Apache 1.1.x
a System
  +V8 and for Apache 1.2.x a POSIX) <A NAME="regexp">regular expression</A>
   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 @@
  -<A name="rhs"><EM>Substitution</EM></A> of a rewriting rule is
the string
  +<A NAME="rhs"><EM>Substitution</EM></A> of a rewriting rule is
the string
   which is substituted for (or replaces) the original URL for which
   <EM>Pattern</EM> matched.  Beside plain text you can use
  @@ -966,7 +965,7 @@
   comma-separated list of the following flags:
(force <A name="redirect"><STRONG>r</STRONG>edirect</A>)<BR>
(force <A NAME="redirect"><STRONG>r</STRONG>edirect</A>)<BR>
       Prefix <EM>Substitution</EM>
       with <CODE>http://thishost[:thisport]/</CODE> (which makes the new URL
a URI) to
       force a external redirection. If no <EM>code</EM> is given a HTTP response
  @@ -1287,14 +1286,10 @@
   <!--/%hypertext -->
  -<A name="Additional">
  -<H1>Additional Features</H1>
  +<H1><A NAME="Additional">Additional Features</A></H1>
  -<A name="EnvVar">
  -<H2>Environment Variables</H2>
  +<H2><A NAME="EnvVar">Environment Variables</A></H2>
   This module keeps track of two additional (non-standard) CGI/SSI environment
   variables named <TT>SCRIPT_URL</TT> and <TT>SCRIPT_URI</TT>. These
  1.7       +1 -1      apache-1.3/htdocs/manual/mod/mod_speling.html
  Index: mod_speling.html
  RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_speling.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- mod_speling.html	1998/02/05 20:04:59	1.6
  +++ mod_speling.html	1998/02/05 21:20:02	1.7
  @@ -57,7 +57,7 @@
     <HR> <!-- the HR is part of the directive description -->
  -  <A name="checkspelling"><H2>CheckSpelling</H2></A>
  +  <H2><A name="checkspelling">CheckSpelling</A></H2>
     <!--%plaintext &lt;?INDEX {\tt CheckSpelling} directive&gt; -->

View raw message