httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r1174747 [4/6] - in /httpd/httpd/trunk/docs/manual: ./ developer/ howto/ misc/ mod/ platform/ programs/ rewrite/ ssl/ style/lang/ vhosts/
Date Fri, 23 Sep 2011 13:36:43 GMT
Modified: httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_rewrite.xml Fri Sep 23 13:36:39 2011
@@ -32,21 +32,21 @@ URLs on the fly</description>
 <identifier>rewrite_module</identifier>
 
 <summary>
-	<p>The <module>mod_rewrite</module> module uses a rule-based rewriting 
+	<p>The <module>mod_rewrite</module> module uses a rule-based rewriting
       engine, based on a regular-expression parser, to rewrite requested URLs on
-      the fly. By default, <module>mod_rewrite</module> maps a URL to a filesystem 
+      the fly. By default, <module>mod_rewrite</module> maps a URL to a filesystem
       path. However, it can also be used to redirect one URL to another URL, or
       to invoke an internal proxy fetch.</p>
-      <p><module>mod_rewrite</module> provides a flexible and powerful way to 
-      manipulate URLs using an unlimited number of rules. Each rule can have an 
+      <p><module>mod_rewrite</module> provides a flexible and powerful way to
+      manipulate URLs using an unlimited number of rules. Each rule can have an
       unlimited number of attached rule conditions, to allow you to rewrite URL
-      based on server variables, environment variables, HTTP headers, or time 
+      based on server variables, environment variables, HTTP headers, or time
       stamps.</p>
       <p><module>mod_rewrite</module> operates on the full URL path, including the
-      path-info section. A rewrite rule can be invoked in 
-      <code>httpd.conf</code> or in <code>.htaccess</code>. The path generated 
-      by a rewrite rule can include a query string, or can lead to internal 
-      sub-processing, external request redirection, or internal proxy 
+      path-info section. A rewrite rule can be invoked in
+      <code>httpd.conf</code> or in <code>.htaccess</code>. The path generated
+      by a rewrite rule can include a query string, or can lead to internal
+      sub-processing, external request redirection, or internal proxy
       throughput.</p>
 
       <p>Further details, discussion, and examples, are provided in the
@@ -142,7 +142,7 @@ later</compatibility>
       <dl>
       <dt><code>Inherit</code></dt>
       <dd>
-      
+
       <p>This forces the current configuration to inherit the
       configuration of the parent. In per-virtual-server context,
       this means that the maps, conditions and rules of the main
@@ -157,7 +157,7 @@ later</compatibility>
       of local rules - has no influence on this behavior. If local
       rules forced the rewriting to stop, the inherited rules won't
       be processed.</p>
-     
+
       <note type="warning">
       Rules inherited from the parent scope are applied
       <strong>after</strong> rules specified in the child scope.
@@ -167,10 +167,10 @@ later</compatibility>
       <dt><code>InheritBefore</code></dt>
       <dd>
       <p> Like <code>Inherit</code> above, but the rules from the parent scope
-      are applied <strong>before</strong> rules specified in the child scope.  
+      are applied <strong>before</strong> rules specified in the child scope.
       Available in Apache HTTP Server 2.3.10 and later.</p>
       </dd>
-      
+
       </dl>
 
 </usage>
@@ -245,7 +245,7 @@ Apache HTTP Server 2.0.41 and later</com
     <dt>dbm</dt>
         <dd>Looks up an entry in a dbm file containing name, value
         pairs. Hash is constructed from a plain text file format using
-        the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code> 
+        the <code><a href="../programs/httxt2dbm.html">httxt2dbm</a></code>
         utility.  (<a href="../rewrite/rewritemap.html#dbm">Details ...</a>)</dd>
 
     <dt>int</dt>
@@ -283,13 +283,13 @@ Apache HTTP Server 2.0.41 and later</com
       that result in the substitution of a relative path.
       When you use a <directive module="mod_rewrite">RewriteRule</directive>
       in a <code>.htaccess</code> file, <module>mod_rewrite</module> strips off
-      the local directory prefix before processing, then rewrites the rest of 
+      the local directory prefix before processing, then rewrites the rest of
       the URL. When the rewrite is completed, <module>mod_rewrite</module>
       automatically adds the local directory prefix (or the
-      <directive>RewriteBase</directive> when set) back on to the substitution 
+      <directive>RewriteBase</directive> when set) back on to the substitution
       before handing it back to the core of the server as if it were the original
       URL.</p>
-      
+
       <p>This directive is <em>required</em> for per-directory rewrites whose context
       is a directory made available via the <directive module="mod_alias">Alias</directive>
       directive, when the substitution uses a relative path.</p>
@@ -300,9 +300,9 @@ Apache HTTP Server 2.0.41 and later</com
       <code>.htaccess</code> file where you want to use <directive
       module="mod_rewrite">RewriteRule</directive> directives.</p>
 
-      <p>The example below demonstrates how to map 
-      http://example.com/myapp/index.html to 
-      /home/www/example/newsite.html, in a <code>.htaccess</code> file. This 
+      <p>The example below demonstrates how to map
+      http://example.com/myapp/index.html to
+      /home/www/example/newsite.html, in a <code>.htaccess</code> file. This
       assumes that the content available at
       http://example.com/ is on disk at /home/www/example/</p>
 <example>
@@ -452,7 +452,7 @@ RewriteRule ^index\.html$  newsite.html
                 Most are documented elsewhere in the Manual or in
                 the CGI specification.</p>
 
-                <p>SERVER_NAME and SERVER_PORT depend on the values of 
+                <p>SERVER_NAME and SERVER_PORT depend on the values of
                 <directive module="core">UseCanonicalName</directive> and
                 <directive module="core">UseCanonicalPhysicalPort</directive>
                 respectively.</p>
@@ -485,7 +485,7 @@ RewriteRule ^index\.html$  newsite.html
                   browser to the server (e.g., "<code>GET
                   /index.html HTTP/1.1</code>"). This does not
                   include any additional headers sent by the
-                  browser.  This value has not been unescaped 
+                  browser.  This value has not been unescaped
                   (decoded), unlike most other variables below.</dd>
 
                   <dt><code>REQUEST_URI</code></dt>
@@ -499,9 +499,9 @@ RewriteRule ^index\.html$  newsite.html
 
                   <dd>The full local filesystem path to the file or
                   script matching the request, if this has already
-                  been determined by the server at the time 
-                  <code>REQUEST_FILENAME</code> is referenced. Otherwise, 
-                  such as when used in virtual host context, the same 
+                  been determined by the server at the time
+                  <code>REQUEST_FILENAME</code> is referenced. Otherwise,
+                  such as when used in virtual host context, the same
                   value as <code>REQUEST_URI</code>.</dd>
 
                   <dt><code>HTTPS</code></dt>
@@ -685,7 +685,7 @@ RewriteRule ^index\.html$  newsite.html
             numerically compared to the <em>CondPattern</em>. True if
             the <em>TestString</em> is numerically greater than or equal
             to the <em>CondPattern</em>.</li>
-            
+
              <li>'<strong>-gt</strong>' (is numerically
             <strong>g</strong>reater <strong>t</strong>han)<br />
             The <em>TestString</em> is treated as an integer, and is
@@ -701,7 +701,7 @@ RewriteRule ^index\.html$  newsite.html
             to the <em>CondPattern</em>. Avoid confusion with the
             <strong>-l</strong> by using the <strong>-L</strong> or
             <strong>-h</strong> variant.</li>
-            
+
              <li>'<strong>-lt</strong>' (is numerically
             <strong>l</strong>ess <strong>t</strong>han)<br />
             The <em>TestString</em> is treated as an integer, and is
@@ -902,16 +902,16 @@ RewriteRule  ^/$                 /homepa
       RewriteRule.</p>
 
 <note><title>What is matched?</title>
-      <p>In <directive module="core">VirtualHost</directive> context, 
+      <p>In <directive module="core">VirtualHost</directive> context,
       The <em>Pattern</em> will initially be matched against the part of the
       URL after the hostname and port, and before the query string (e.g. "/app1/index.html").</p>
 
       <p>In <directive module="core">Directory</directive> and htaccess context,
-      the <em>Pattern</em> will initially be matched against the  
+      the <em>Pattern</em> will initially be matched against the
       <em>filesystem</em> path, after removing the prefix that lead the server
-      to the current <directive>RewriteRule</directive> (e.g. "app1/index.html" 
+      to the current <directive>RewriteRule</directive> (e.g. "app1/index.html"
       or "index.html" depending on where the directives are defined).</p>
-       
+
       <p>If you wish to match against the hostname, port, or query string, use a
       <directive module="mod_rewrite">RewriteCond</directive> with the
       <code>%{HTTP_HOST}</code>, <code>%{SERVER_PORT}</code>, or
@@ -937,12 +937,12 @@ restriction is required for security rea
 per-directory prefix (which always is the same for a specific
 directory) is automatically <em>removed</em> for the RewriteRule pattern matching
 and automatically <em>added</em> after any relative (not starting with a
-slash or protocol name) substitution encounters the end of a rule set.  
-See the <directive module="mod_rewrite">RewriteBase</directive> 
-directive for more information regarding what prefix will be added back to 
+slash or protocol name) substitution encounters the end of a rule set.
+See the <directive module="mod_rewrite">RewriteBase</directive>
+directive for more information regarding what prefix will be added back to
 relative substutions.</li>
 
-<li> If you wish to match against the full URL-path in a per-directory 
+<li> If you wish to match against the full URL-path in a per-directory
 (htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
 a <directive>RewriteCond</directive>.</li>
 
@@ -1100,14 +1100,14 @@ cannot use <code>$N</code> in the substi
     </tr>
     <tr>
         <td>cookie|CO=<em>NAME</em>:<em>VAL</em></td>
-        <td>Sets a cookie in the client browser. Full syntax is: 
+        <td>Sets a cookie in the client browser. Full syntax is:
         CO=<em>NAME</em>:<em>VAL</em>:<em>domain</em>[:<em>lifetime</em>[:<em>path</em>[:<em>secure</em>[:<em>httponly</em>]]]] <em><a href="../rewrite/flags.html#flag_co">details ...</a></em>
         </td>
     </tr>
     <tr>
         <td>discardpath|DPI</td>
         <td>Causes the PATH_INFO portion of the rewritten URI to be
-        discarded. <em><a href="../rewrite/flags.html#flag_dpi">details 
+        discarded. <em><a href="../rewrite/flags.html#flag_dpi">details
         ...</a></em></td>
     </tr>
     <tr>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_session.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session.xml Fri Sep 23 13:36:39 2011
@@ -42,7 +42,7 @@
     interface. Sessions can be used for keeping track of whether a user
     has been logged in, or for other per user information that should
     be kept available across requests.</p>
-    
+
     <p>Sessions may be stored on the server, or may be stored on the
     browser. Sessions may also be optionally encrypted for added security.
     These features are divided into several modules in addition to
@@ -55,7 +55,7 @@
     <p>Sessions may be manipulated from other modules that depend on the
     session, or the session may be read from and written to using
     environment variables and HTTP headers, as appropriate.</p>
-    
+
 </summary>
 <seealso><module>mod_session_cookie</module></seealso>
 <seealso><module>mod_session_crypto</module></seealso>
@@ -64,10 +64,10 @@
     <section id="whatisasession"><title>What is a session?</title>
       <p>At the core of the session interface is a table of key and value pairs
       that are made accessible across browser requests.</p>
-      
+
       <p>These pairs can be set to any valid string, as needed by the
       application making use of the session.</p>
-      
+
     </section>
     <section id="whocanuseasession"><title>Who can use a session?</title>
       <p>The session interface is primarily developed for the use by other
@@ -82,31 +82,31 @@
       <p>Apache can be configured to keep track of per user sessions stored
       on a particular server or group of servers. This functionality is
       similar to the sessions available in typical application servers.</p>
-      
+
       <p>If configured, sessions are tracked through the use of a session ID that
       is stored inside a cookie, or extracted from the parameters embedded
       within the URL query string, as found in a typical GET request.</p>
-      
+
       <p>As the contents of the session are stored exclusively on the server,
       there is an expectation of privacy of the contents of the session. This
       does have performance and resource implications should a large number
       of sessions be present, or where a large number of webservers have to
       share sessions with one another.</p>
-      
+
       <p>The <module>mod_session_dbd</module> module allows the storage of user
       sessions within a SQL database via <module>mod_dbd</module>.</p>
 
     </section> <!-- /serversession -->
-    
+
     <section id="browsersession"><title>Keeping sessions on the browser</title>
       <p>Where keeping track of a session on a server is too resource
       intensive or inconvenient, the option exists to store the contents
       of the session within a cookie on the client browser instead.</p>
-      
+
       <p>This has the advantage that minimal resources are required on the
       server to keep track of sessions, and multiple servers within a server
       farm have no need to share session information.</p>
-      
+
       <p>The contents of the session however are exposed to the client, with a
       corresponding risk of a loss of privacy. The
       <module>mod_session_crypto</module> module can be configured to encrypt the
@@ -118,11 +118,11 @@
     </section> <!-- /browsersession -->
 
     <section id="basicexamples"><title>Basic Examples</title>
-    
+
       <p>Creating a session is as simple as turning the session on, and deciding
       where the session will be stored. In this example, the session will be
       stored on the browser, in a cookie called <code>session</code>.</p>
-      
+
       <example><title>Browser based session</title>
         Session On<br />
         SessionCookieName session path=/<br />
@@ -132,7 +132,7 @@
       following example shows how values can be injected into the session through
       the use of a predetermined HTTP response header called
       <code>X-Replace-Session</code>.</p>
-      
+
       <example><title>Writing to a session</title>
         Session On<br />
         SessionCookieName session path=/<br />
@@ -142,7 +142,7 @@
       <p>The header should contain name value pairs expressed in the same format
       as a query string in a URL, as in the example below. Setting a key to the
       empty string has the effect of removing that key from the session.</p>
-      
+
       <example><title>CGI to write to a session</title>
         #!/bin/bash<br />
         echo "Content-Type: text/plain"<br />
@@ -155,7 +155,7 @@
       environment variable. By default, the session is kept private, so this
       has to be explicitly turned on with the
       <directive module="mod_session">SessionEnv</directive> directive.</p>
-      
+
       <example><title>Read from a session</title>
         Session On<br />
         SessionEnv On<br />
@@ -168,32 +168,32 @@
 
     </section>
     <section id="sessionprivacy"><title>Session Privacy</title>
-    
+
       <p>Using the "show cookies" feature of your browser, you would have seen
       a clear text representation of the session. This could potentially be a
       problem should the end user need to be kept unaware of the contents of
       the session, or where a third party could gain unauthorised access to the
       data within the session.</p>
-      
+
       <p>The contents of the session can be optionally encrypted before being
       placed on the browser using the <module>mod_session_crypto</module>
       module.</p>
-      
+
       <example><title>Browser based encrypted session</title>
         Session On<br />
         SessionCryptoPassphrase secret<br />
         SessionCookieName session path=/<br />
       </example>
-      
+
       <p>The session will be automatically decrypted on load, and encrypted on
       save by Apache, the underlying application using the session need have
       no knowledge that encryption is taking place.</p>
-      
+
       <p>Sessions stored on the server rather than on the browser can also be
       encrypted as needed, offering privacy where potentially sensitive
       information is being shared between webservers in a server farm using
       the <module>mod_session_dbd</module> module.</p>
-      
+
     </section>
     <section id="cookieprivacy"><title>Cookie Privacy</title>
 
@@ -201,7 +201,7 @@
       ability to restrict cookie transport to SSL protected pages only, or
       to prevent browser based javascript from gaining access to the contents
       of the cookie.</p>
-      
+
       <note type="warning"><title>Warning</title>
       <p>Some of the HTTP cookie privacy features are either non-standard, or
       are not implemented consistently across browsers. The session modules
@@ -214,13 +214,13 @@
 
       <p>Standard cookie parameters can be specified after the name of the cookie,
       as in the example below.</p>
-      
+
       <example><title>Setting cookie parameters</title>
         Session On<br />
         SessionCryptoPassphrase secret<br />
         SessionCookieName session path=/private;domain=example.com;httponly;secure;<br />
       </example>
-      
+
       <p>In cases where the Apache server forms the frontend for backend origin servers,
       it is possible to have the session cookies removed from the incoming HTTP headers using
       the <directive module="mod_session_cookie">SessionCookieRemove</directive> directive.
@@ -246,7 +246,7 @@
         AuthName realm<br />
         ...<br />
       </example>
-      
+
       <p>See the <module>mod_auth_form</module> module for documentation and complete
       examples.</p>
 
@@ -289,7 +289,7 @@
     the session, the session will time out and be removed. Where a session is
     used to stored user login details, this has the effect of logging the user
     out automatically after the given time.</p>
-    
+
     <p>Setting the maxage to zero disables session expiry.</p>
 </usage>
 </directivesynopsis>
@@ -310,7 +310,7 @@
     <p>If set to <var>On</var>, the <directive>SessionEnv</directive> directive
     causes the contents of the session to be written to a CGI environment
     variable called <var>HTTP_SESSION</var>.</p>
-    
+
     <p>The string is written in the URL query format, for example:</p>
 
     <example>
@@ -335,13 +335,13 @@
     <p>The <directive>SessionHeader</directive> directive defines the name of an
     HTTP response header which, if present, will be parsed and written to the
     current session.</p>
-    
+
     <p>The header value is expected to be in the URL query format, for example:</p>
 
     <example>
       <code>key1=foo&amp;key2=&amp;key3=bar</code>
     </example>
-    
+
     <p>Where a key is set to the empty string, that key will be removed from the
     session.</p>
 
@@ -365,7 +365,7 @@
     website more efficient, by targeting a more precise URL space for which
     a session should be maintained. By default, all URLs within the directory
     or location are included in the session.</p>
-    
+
     <note type="warning"><title>Warning</title>
     <p>This directive has a similar purpose to the <var>path</var> attribute
     in HTTP cookies, but should not be confused with this attribute. This

Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_cookie.xml Fri Sep 23 13:36:39 2011
@@ -40,38 +40,38 @@
 
     <p>This submodule of <module>mod_session</module> provides support for the
     storage of user sessions on the remote browser within HTTP cookies.</p>
-    
+
     <p>Using cookies to store a session removes the need for the server or
     a group of servers to store the session locally, or collaborate to share
     a session, and can be useful for high traffic environments where a
     server based session might be too resource intensive.</p>
-    
+
     <p>If session privacy is required, the <module>mod_session_crypto</module>
     module can be used to encrypt the contents of the session before writing
     the session to the client.</p>
-    
+
     <p>For more details on the session interface, see the documentation for
     the <module>mod_session</module> module.</p>
-    
+
 </summary>
 <seealso><module>mod_session</module></seealso>
 <seealso><module>mod_session_crypto</module></seealso>
 <seealso><module>mod_session_dbd</module></seealso>
 
     <section id="basicexamples"><title>Basic Examples</title>
-    
+
       <p>To create a simple session and store it in a cookie called
       <var>session</var>, configure the session as follows:</p>
-      
+
       <example><title>Browser based session</title>
         Session On<br />
         SessionCookieName session path=/<br />
       </example>
-      
+
       <p>For more examples on how the session can be configured to be read
       from and written to by a CGI application, see the
       <module>mod_session</module> examples section.</p>
-      
+
       <p>For documentation on how the session can be used to store username
       and password details, see the <module>mod_auth_form</module> module.</p>
 
@@ -93,12 +93,12 @@
     optional attributes of an RFC2109 compliant cookie inside which the session will
     be stored. RFC2109 cookies are set using the <code>Set-Cookie</code> HTTP header.
     </p>
-    
+
     <p>An optional list of cookie attributes can be specified, as per the example below.
     These attributes are inserted into the cookie as is, and are not interpreted by
     Apache. Ensure that your attributes are defined correctly as per the cookie specification.
     </p>
-    
+
     <example><title>Cookie with attributes</title>
       Session On<br />
       SessionCookieName session path=/private;domain=example.com;httponly;secure;version=1;<br />
@@ -123,12 +123,12 @@
     optional attributes of an RFC2965 compliant cookie inside which the session will
     be stored. RFC2965 cookies are set using the <code>Set-Cookie2</code> HTTP header.
     </p>
-    
+
     <p>An optional list of cookie attributes can be specified, as per the example below.
     These attributes are inserted into the cookie as is, and are not interpreted by
     Apache. Ensure that your attributes are defined correctly as per the cookie specification.
     </p>
-    
+
     <example><title>Cookie2 with attributes</title>
       Session On<br />
       SessionCookieName2 session path=/private;domain=example.com;httponly;secure;version=1;<br />
@@ -151,7 +151,7 @@
 <usage>
     <p>The <directive>SessionCookieRemove</directive> flag controls whether the cookies
     containing the session will be removed from the headers during request processing.</p>
-    
+
     <p>In a reverse proxy situation where the Apache server acts as a server frontend for
     a backend origin server, revealing the contents of the session cookie to the backend
     could be a potential privacy violation. When set to on, the session cookie will be

Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_crypto.xml Fri Sep 23 13:36:39 2011
@@ -41,37 +41,37 @@
     <p>This submodule of <module>mod_session</module> provides support for the
     encryption of user sessions before being written to a local database, or
     written to a remote browser via an HTTP cookie.</p>
-    
+
     <p>This can help provide privacy to user sessions where the contents of
     the session should be kept private from the user, or where protection is
     needed against the effects of cross site scripting attacks.</p>
-    
+
     <p>For more details on the session interface, see the documentation for
     the <module>mod_session</module> module.</p>
-    
+
 </summary>
 <seealso><module>mod_session</module></seealso>
 <seealso><module>mod_session_cookie</module></seealso>
 <seealso><module>mod_session_dbd</module></seealso>
 
     <section id="basicusage"><title>Basic Usage</title>
-    
+
       <p>To create a simple encrypted session and store it in a cookie called
       <var>session</var>, configure the session as follows:</p>
-      
+
       <example><title>Browser based encrypted session</title>
         Session On<br />
         SessionCookieName session path=/<br />
         SessionCryptoPassphrase secret
       </example>
-      
+
       <p>The session will be encrypted with the given key. Different servers can
       be configured to share sessions by ensuring the same encryption key is used
       on each server.</p>
-      
+
       <p>If the encryption key is changed, sessions will be invalidated
       automatically.</p>
-      
+
       <p>For documentation on how the session can be used to store username
       and password details, see the <module>mod_auth_form</module> module.</p>
 
@@ -146,7 +146,7 @@
     <p>The cipher can be set to <var>3des192</var> or <var>aes256</var> using the
     <var>cipher</var> parameter as per the example below. If not set, the cipher defaults
     to <var>aes256</var>.</p>
-    
+
     <example><title>Cipher</title>
       SessionCryptoPassphrase secret cipher=aes256
     </example>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_session_dbd.xml Fri Sep 23 13:36:39 2011
@@ -49,13 +49,13 @@
 
     <p>SQL based sessions are hidden from the browser, and so offer a measure of
     privacy without the need for encryption.</p>
-    
+
     <p>Different webservers within a server farm may choose to share a database,
     and so share sessions with one another.</p>
-    
+
     <p>For more details on the session interface, see the documentation for
     the <module>mod_session</module> module.</p>
-    
+
 </summary>
 <seealso><module>mod_session</module></seealso>
 <seealso><module>mod_session_crypto</module></seealso>
@@ -67,7 +67,7 @@
       <p>Before the <module>mod_session_dbd</module> module can be configured to maintain a
       session, the <module>mod_dbd</module> module must be configured to make the various database queries
       available to the server.</p>
-      
+
       <p>There are four queries required to keep a session maintained, to select an existing session,
       to update an existing session, to insert a new session, and to delete an expired or empty
       session. These queries are configured as per the example below.</p>
@@ -85,58 +85,58 @@
     </section>
 
     <section id="anonymous"><title>Anonymous Sessions</title>
-    
+
       <p>Anonymous sessions are keyed against a unique UUID, and stored on the
       browser within an HTTP cookie. This method is similar to that used by most
       application servers to store session information.</p>
-    
+
       <p>To create a simple anonymous session and store it in a postgres database
       table called <var>apachesession</var>, and save the session ID in a cookie
       called <var>session</var>, configure the session as follows:</p>
-      
+
       <example><title>SQL based anonymous session</title>
         Session On<br />
         SessionDBDCookieName session path=/<br />
       </example>
-      
+
       <p>For more examples on how the session can be configured to be read
       from and written to by a CGI application, see the
       <module>mod_session</module> examples section.</p>
-      
+
       <p>For documentation on how the session can be used to store username
       and password details, see the <module>mod_auth_form</module> module.</p>
 
     </section>
 
     <section id="peruser"><title>Per User Sessions</title>
-    
+
       <p>Per user sessions are keyed against the username of a successfully
       authenticated user. It offers the most privacy, as no external handle
       to the session exists outside of the authenticated realm.</p>
-      
+
       <p>Per user sessions work within a correctly configured authenticated
       environment, be that using basic authentication, digest authentication
       or SSL client certificates. Due to the limitations of who came first,
       the chicken or the egg, per user sessions cannot be used to store
       authentication credentials from a module like
       <module>mod_auth_form</module>.</p>
-    
+
       <p>To create a simple per user session and store it in a postgres database
       table called <var>apachesession</var>, and with the session keyed to the
       userid, configure the session as follows:</p>
-      
+
       <example><title>SQL based per user session</title>
         Session On<br />
         SessionDBDPerUser On<br />
       </example>
-      
+
     </section>
 
     <section id="housekeeping"><title>Database Housekeeping</title>
       <p>Over the course of time, the database can be expected to start accumulating
       expired sessions. At this point, the <module>mod_session_dbd</module> module
       is not yet able to handle session expiry automatically.</p>
-      
+
       <note type="warning"><title>Warning</title>
       <p>The administrator will need to set up an external process via cron to clean
       out expired sessions.</p>
@@ -190,12 +190,12 @@
     optional attributes of an RFC2965 compliant cookie inside which the session ID will
     be stored. RFC2965 cookies are set using the <code>Set-Cookie2</code> HTTP header.
     </p>
-    
+
     <p>An optional list of cookie attributes can be specified, as per the example below.
     These attributes are inserted into the cookie as is, and are not interpreted by
     Apache. Ensure that your attributes are defined correctly as per the cookie specification.
     </p>
-    
+
     <example><title>Cookie2 with attributes</title>
       Session On<br />
       SessionDBDCookieName2 session path=/private;domain=example.com;httponly;secure;version=1;<br />

Modified: httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_setenvif.xml Fri Sep 23 13:36:39 2011
@@ -70,8 +70,8 @@ on characteristics of the request</descr
   <code>User-Agent</code> HTTP request header.  The following two
   lines have the same effect:</p>
 <example>
-   BrowserMatchNoCase Robot is_a_robot<br /> 
-   SetEnvIfNoCase User-Agent Robot is_a_robot<br /> 
+   BrowserMatchNoCase Robot is_a_robot<br />
+   SetEnvIfNoCase User-Agent Robot is_a_robot<br />
 </example>
 
     <p>Some additional examples:</p>
@@ -140,7 +140,7 @@ respect to case</description>
 <li>An HTTP request header field (see <a
     href="http://www.rfc-editor.org/rfc/rfc2616.txt">RFC2616</a>
     for more information about these); for example: <code>Host</code>,
-    <code>User-Agent</code>, <code>Referer</code>, and 
+    <code>User-Agent</code>, <code>Referer</code>, and
     <code>Accept-Language</code>.  A regular expression may be
     used to specify a set of request headers.</li>
 
@@ -301,7 +301,7 @@ results.</seealso>
 <name>SetEnvIfNoCase</name>
 <description>Sets environment variables based on attributes of the request
 without respect to case</description>
-<syntax>SetEnvIfNoCase <em>attribute regex 
+<syntax>SetEnvIfNoCase <em>attribute regex
         [!]env-variable</em>[=<em>value</em>]
     [[!]<em>env-variable</em>[=<em>value</em>]] ...</syntax>
 <contextlist><context>server config</context>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_so.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_so.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_so.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_so.xml Fri Sep 23 13:36:39 2011
@@ -28,7 +28,7 @@ modules into the server at start-up or r
 <status>Extension</status>
 <sourcefile>mod_so.c</sourcefile>
 <identifier>so_module</identifier>
-<compatibility>This is a Base module (always included) on 
+<compatibility>This is a Base module (always included) on
 Windows</compatibility>
 
 <summary>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_speling.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_speling.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_speling.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_speling.xml Fri Sep 23 13:36:39 2011
@@ -66,7 +66,7 @@ misspellings.</description>
 
 <directivesynopsis>
 <name>CheckSpelling</name>
-<description>Enables the spelling 
+<description>Enables the spelling
 module</description>
 <syntax>CheckSpelling on|off</syntax>
 <default>CheckSpelling Off</default>
@@ -126,7 +126,7 @@ module</description>
 <override>Options</override>
 
 <usage>
-    <p>When set, this directive limits the action of the spelling correction to lower/upper case changes. 
+    <p>When set, this directive limits the action of the spelling correction to lower/upper case changes.
     Other potential corrections are not performed.</p>
 
 </usage>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml Fri Sep 23 13:36:39 2011
@@ -43,10 +43,10 @@ to provide the cryptography engine.</p>
 
 <section id="envvars"><title>Environment Variables</title>
 
-<p>This module can be configured to provide several items of SSL information 
+<p>This module can be configured to provide several items of SSL information
 as additional environment variables to the SSI and CGI namespace. This
 information is not provided by default for performance reasons. (See
-<directive>SSLOptions</directive> StdEnvVars, below.) The generated variables 
+<directive>SSLOptions</directive> StdEnvVars, below.) The generated variables
 are listed in the table below. For backward compatibility the information can
 be made available under different names, too. Look in the <a
 href="../ssl/ssl_compat.html">Compatibility</a> chapter for details on the
@@ -146,7 +146,7 @@ REQUEST_URI            REMOTE_USER</pre>
   <dt><code>ENV:<em>variablename</em></code></dt>
   <dd>This will expand to the standard environment
   variable <em>variablename</em>.</dd>
-  
+
   <dt><code>HTTP:<em>headername</em></code></dt>
   <dd>This will expand to the value of the request header with name
   <em>headername</em>.</dd>
@@ -158,7 +158,7 @@ REQUEST_URI            REMOTE_USER</pre>
 
 <p>When <module>mod_ssl</module> is built into Apache or at least
 loaded (under DSO situation) additional functions exist for the <a
-href="mod_log_config.html#formats">Custom Log Format</a> of 
+href="mod_log_config.html#formats">Custom Log Format</a> of
 <module>mod_log_config</module>. First there is an
 additional ``<code>%{</code><em>varname</em><code>}x</code>''
 eXtension format function which can be used to expand any variables
@@ -241,7 +241,7 @@ string in <module>mod_log_config</module
 
 <directivesynopsis>
 <name>SSLPassPhraseDialog</name>
-<description>Type of pass phrase dialog for encrypted private 
+<description>Type of pass phrase dialog for encrypted private
 keys</description>
 <syntax>SSLPassPhraseDialog <em>type</em></syntax>
 <default>SSLPassPhraseDialog builtin</default>
@@ -278,7 +278,7 @@ query can be done in two ways which can 
     dialog (i.e. when you use a single Pass Phrase for all N Private Key files
     this Pass Phrase is queried only once).</p></li>
 
-<li><code>|/path/to/program [args...]</code> 
+<li><code>|/path/to/program [args...]</code>
 
    <p>This mode allows an external program to be used which acts as a
    pipe to a particular input device; the program is sent the standard
@@ -319,9 +319,9 @@ SSLPassPhraseDialog exec:/usr/local/apac
 
 <directivesynopsis>
 <name>SSLRandomSeed</name>
-<description>Pseudo Random Number Generator (PRNG) seeding 
+<description>Pseudo Random Number Generator (PRNG) seeding
 source</description>
-<syntax>SSLRandomSeed <em>context</em> <em>source</em> 
+<syntax>SSLRandomSeed <em>context</em> <em>source</em>
 [<em>bytes</em>]</syntax>
 <contextlist><context>server config</context></contextlist>
 
@@ -414,7 +414,7 @@ SSLRandomSeed connect file:/dev/urandom 
 
 <directivesynopsis>
 <name>SSLSessionCache</name>
-<description>Type of the global/inter-process SSL Session 
+<description>Type of the global/inter-process SSL Session
 Cache</description>
 <syntax>SSLSessionCache <em>type</em></syntax>
 <default>SSLSessionCache none</default>
@@ -527,9 +527,9 @@ SSLEngine on<br />
 ...<br />
 &lt;/VirtualHost&gt;
 </example>
-<p>In Apache 2.1 and later, <directive>SSLEngine</directive> can be set to 
-<code>optional</code>. This enables support for 
-<a href="http://www.ietf.org/rfc/rfc2817.txt">RFC 2817</a>, Upgrading to TLS 
+<p>In Apache 2.1 and later, <directive>SSLEngine</directive> can be set to
+<code>optional</code>. This enables support for
+<a href="http://www.ietf.org/rfc/rfc2817.txt">RFC 2817</a>, Upgrading to TLS
 Within HTTP/1.1. At this time no web browsers support RFC 2817.</p>
 </usage>
 </directivesynopsis>
@@ -545,7 +545,7 @@ Within HTTP/1.1. At this time no web bro
 <p>
 This directive toggles the usage of the SSL library FIPS_mode flag.
 It must be set in the global server context and cannot be configured
-with conflicting settings (SSLFIPS on followed by SSLFIPS off or 
+with conflicting settings (SSLFIPS on followed by SSLFIPS off or
 similar).  The mode applies to all SSL library operations.
 </p>
 <p>
@@ -571,7 +571,7 @@ by the applicable Security Policy.
 
 <usage>
 <p>
-This directive can be used to control which versions of the SSL protocol 
+This directive can be used to control which versions of the SSL protocol
 will be accepted in new connections.</p>
 <p>
 The available (case-insensitive) <em>protocol</em>s are:</p>
@@ -585,21 +585,21 @@ The available (case-insensitive) <em>pro
 <li><code>SSLv3</code>
     <p>
     This is the Secure Sockets Layer (SSL) protocol, version 3.0, from
-    the Netscape Corporation. 
+    the Netscape Corporation.
     It is the successor to SSLv2 and the predecessor to TLSv1. It's supported by
     almost all popular browsers.</p></li>
 
 <li><code>TLSv1</code>
     <p>
     This is the Transport Layer Security (TLS) protocol, version 1.0. It is the
-    successor to SSLv3 and is defined in <a href="http://www.ietf.org/rfc/rfc2246.txt">RFC2246</a>. 
+    successor to SSLv3 and is defined in <a href="http://www.ietf.org/rfc/rfc2246.txt">RFC2246</a>.
     Which has been obsoleted by <a href="http://www.ietf.org/rfc/rfc4346.txt">RFC4346</a>.</p></li>
 
 <li><code>All</code>
     <p>
     This is a shortcut for ``<code>+SSLv2 +SSLv3 +TLSv1</code>'' and a
     convenient way for enabling all protocols except one when used in
-    combination with the minus sign on a protocol as the example above 
+    combination with the minus sign on a protocol as the example above
     shows.</p></li>
 </ul>
 <example><title>Example</title>
@@ -611,7 +611,7 @@ SSLProtocol all -SSLv2
 
 <directivesynopsis>
 <name>SSLCipherSuite</name>
-<description>Cipher Suite available for negotiation in SSL 
+<description>Cipher Suite available for negotiation in SSL
 handshake</description>
 <syntax>SSLCipherSuite <em>cipher-spec</em></syntax>
 <default>SSLCipherSuite DEFAULT (depends on OpenSSL version)</default>
@@ -864,7 +864,7 @@ SSLCertificateChainFile /usr/local/apach
 
 <directivesynopsis>
 <name>SSLCACertificatePath</name>
-<description>Directory of PEM-encoded CA Certificates for 
+<description>Directory of PEM-encoded CA Certificates for
 Client Auth</description>
 <syntax>SSLCACertificatePath <em>directory-path</em></syntax>
 <contextlist><context>server config</context>
@@ -890,7 +890,7 @@ SSLCACertificatePath /usr/local/apache2/
 
 <directivesynopsis>
 <name>SSLCACertificateFile</name>
-<description>File of concatenated PEM-encoded CA Certificates 
+<description>File of concatenated PEM-encoded CA Certificates
 for Client Auth</description>
 <syntax>SSLCACertificateFile <em>file-path</em></syntax>
 <contextlist><context>server config</context>
@@ -902,7 +902,7 @@ This directive sets the <em>all-in-one</
 Certificates of Certification Authorities (CA) whose <em>clients</em> you deal
 with. These are used for Client Authentication. Such a file is simply the
 concatenation of the various PEM-encoded Certificate files, in order of
-preference. This can be used alternatively and/or additionally to 
+preference. This can be used alternatively and/or additionally to
 <directive module="mod_ssl">SSLCACertificatePath</directive>.</p>
 <example><title>Example</title>
 SSLCACertificateFile /usr/local/apache2/conf/ssl.crt/ca-bundle-client.crt
@@ -912,7 +912,7 @@ SSLCACertificateFile /usr/local/apache2/
 
 <directivesynopsis>
 <name>SSLCADNRequestFile</name>
-<description>File of concatenated PEM-encoded CA Certificates 
+<description>File of concatenated PEM-encoded CA Certificates
 for defining acceptable CA names</description>
 <syntax>SSLCADNRequestFile <em>file-path</em></syntax>
 <contextlist><context>server config</context>
@@ -957,7 +957,7 @@ SSLCADNRequestFile /usr/local/apache2/co
 
 <directivesynopsis>
 <name>SSLCADNRequestPath</name>
-<description>Directory of PEM-encoded CA Certificates for 
+<description>Directory of PEM-encoded CA Certificates for
 defining acceptable CA names</description>
 <syntax>SSLCADNRequestPath <em>directory-path</em></syntax>
 <contextlist><context>server config</context>
@@ -986,7 +986,7 @@ SSLCADNRequestPath /usr/local/apache2/co
 
 <directivesynopsis>
 <name>SSLCARevocationPath</name>
-<description>Directory of PEM-encoded CA CRLs for 
+<description>Directory of PEM-encoded CA CRLs for
 Client Auth</description>
 <syntax>SSLCARevocationPath <em>directory-path</em></syntax>
 <contextlist><context>server config</context>
@@ -1012,7 +1012,7 @@ SSLCARevocationPath /usr/local/apache2/c
 
 <directivesynopsis>
 <name>SSLCARevocationFile</name>
-<description>File of concatenated PEM-encoded CA CRLs for 
+<description>File of concatenated PEM-encoded CA CRLs for
 Client Auth</description>
 <syntax>SSLCARevocationFile <em>file-path</em></syntax>
 <contextlist><context>server config</context>
@@ -1116,7 +1116,7 @@ SSLVerifyClient require
 
 <directivesynopsis>
 <name>SSLVerifyDepth</name>
-<description>Maximum depth of CA Certificates in Client 
+<description>Maximum depth of CA Certificates in Client
 Certificate verification</description>
 <syntax>SSLVerifyDepth <em>number</em></syntax>
 <default>SSLVerifyDepth 1</default>
@@ -1260,7 +1260,7 @@ SSLOptions +FakeBasicAuth -StrictRequire
 
 <directivesynopsis>
 <name>SSLRequireSSL</name>
-<description>Deny access when SSL is not used for the 
+<description>Deny access when SSL is not used for the
 HTTP request</description>
 <syntax>SSLRequireSSL</syntax>
 <contextlist><context>directory</context>
@@ -1282,7 +1282,7 @@ SSLRequireSSL
 
 <directivesynopsis>
 <name>SSLRequire</name>
-<description>Allow access only when an arbitrarily complex 
+<description>Allow access only when an arbitrarily complex
 boolean expression is true</description>
 <syntax>SSLRequire <em>expression</em></syntax>
 <contextlist><context>directory</context>
@@ -1499,8 +1499,8 @@ comes with mod_ssl to accomplish this ta
 </note>
 <example><title>Example</title>
 SSLProxyMachineCertificatePath /usr/local/apache2/conf/proxy.crt/
-</example> 
-</usage> 
+</example>
+</usage>
 </directivesynopsis>
 
 
@@ -1713,7 +1713,7 @@ for additional information.
 
 <directivesynopsis>
 <name>SSLProxyCipherSuite</name>
-<description>Cipher Suite available for negotiation in SSL 
+<description>Cipher Suite available for negotiation in SSL
 proxy handshake</description>
 <syntax>SSLProxyCipherSuite <em>cipher-spec</em></syntax>
 <default>SSLProxyCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP</default>
@@ -1731,7 +1731,7 @@ for additional information.</p>
 </directivesynopsis>
 <directivesynopsis>
 <name>SSLProxyCACertificatePath</name>
-<description>Directory of PEM-encoded CA Certificates for 
+<description>Directory of PEM-encoded CA Certificates for
 Remote Server Auth</description>
 <syntax>SSLProxyCACertificatePath <em>directory-path</em></syntax>
 <contextlist><context>server config</context>
@@ -1757,7 +1757,7 @@ SSLProxyCACertificatePath /usr/local/apa
 
 <directivesynopsis>
 <name>SSLProxyCACertificateFile</name>
-<description>File of concatenated PEM-encoded CA Certificates 
+<description>File of concatenated PEM-encoded CA Certificates
 for Remote Server Auth</description>
 <syntax>SSLProxyCACertificateFile <em>file-path</em></syntax>
 <contextlist><context>server config</context>
@@ -1769,7 +1769,7 @@ This directive sets the <em>all-in-one</
 Certificates of Certification Authorities (CA) whose <em>remote servers</em> you deal
 with. These are used for Remote Server Authentication. Such a file is simply the
 concatenation of the various PEM-encoded Certificate files, in order of
-preference. This can be used alternatively and/or additionally to 
+preference. This can be used alternatively and/or additionally to
 <directive module="mod_ssl">SSLProxyCACertificatePath</directive>.</p>
 <example><title>Example</title>
 SSLProxyCACertificateFile /usr/local/apache2/conf/ssl.crt/ca-bundle-remote-server.crt
@@ -1779,7 +1779,7 @@ SSLProxyCACertificateFile /usr/local/apa
 
 <directivesynopsis>
 <name>SSLProxyCARevocationPath</name>
-<description>Directory of PEM-encoded CA CRLs for 
+<description>Directory of PEM-encoded CA CRLs for
 Remote Server Auth</description>
 <syntax>SSLProxyCARevocationPath <em>directory-path</em></syntax>
 <contextlist><context>server config</context>
@@ -1805,7 +1805,7 @@ SSLProxyCARevocationPath /usr/local/apac
 
 <directivesynopsis>
 <name>SSLProxyCARevocationFile</name>
-<description>File of concatenated PEM-encoded CA CRLs for 
+<description>File of concatenated PEM-encoded CA CRLs for
 Remote Server Auth</description>
 <syntax>SSLProxyCARevocationFile <em>file-path</em></syntax>
 <contextlist><context>server config</context>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_status.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_status.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_status.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_status.xml Fri Sep 23 13:36:39 2011
@@ -64,8 +64,8 @@ performance</description>
       <li>The current hosts and requests being processed (*)</li>
     </ul>
 
-    <p>The lines marked "(*)" are only available if 
-    <directive module="core">ExtendedStatus</directive> 
+    <p>The lines marked "(*)" are only available if
+    <directive module="core">ExtendedStatus</directive>
     is <code>On</code>.  In version 2.3.6, loading mod_status will
     toggle <directive module="core">ExtendedStatus</directive> On
     by default.</p>
@@ -109,7 +109,7 @@ performance</description>
     accessing the page
     <code>http://your.server.name/server-status?auto</code>. This
     is useful when automatically run, see the Perl program
-    <code>log_server_status</code>, which you will find in the 
+    <code>log_server_status</code>, which you will find in the
     <code>/support</code> directory of your Apache HTTP Server installation.</p>
 
     <note>
@@ -125,7 +125,7 @@ performance</description>
 
 <section id="troubleshoot">
     <title>Using server-status to troubleshoot</title>
-    
+
     <p>The <code>server-status</code> page may be used as a starting
     place for troubleshooting a situation where your server is consuming
     all available resources (CPU or memory), and you wish to identify

Modified: httpd/httpd/trunk/docs/manual/mod/mod_substitute.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_substitute.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_substitute.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_substitute.xml Fri Sep 23 13:36:39 2011
@@ -46,10 +46,10 @@
 <usage>
     <p>The <directive>Substitute</directive> directive specifies a
     search and replace pattern to apply to the response body.</p>
-    
+
     <p>The meaning of the pattern can be modified by using any
     combination of these flags:</p>
-    
+
     <dl>
         <dt><code>i</code></dt>
         <dd>Perform a case-insensitive match.</dd>
@@ -69,7 +69,7 @@
         that the result of one substitution will ever match a pattern
         or regex of a subsequent one.</dd>
     </dl>
-    
+
     <example><title>Example</title>
         &lt;Location /&gt;
         <indent>
@@ -78,10 +78,10 @@
         </indent>
         &lt;/Location&gt;
     </example>
-    
+
     <p>If either the pattern or the substitution contain a slash
     character then an alternative delimiter should be used:</p>
-    
+
     <example><title>Example of using an alternate delimiter</title>
         &lt;Location /&gt;
         <indent>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_userdir.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_userdir.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_userdir.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_userdir.xml Fri Sep 23 13:36:39 2011
@@ -160,7 +160,7 @@ host</context></contextlist>
     directive was present.</p>
 
     <note><title>Merging details</title>
-    <p> Lists of specific enabled and disabled users are replaced, not merged, 
+    <p> Lists of specific enabled and disabled users are replaced, not merged,
     from global to virtual host scope</p></note>
 
 </usage>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_usertrack.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_usertrack.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_usertrack.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_usertrack.xml Fri Sep 23 13:36:39 2011
@@ -68,20 +68,20 @@
 
     <p>The domain string <strong>must</strong> begin with a dot, and
     <strong>must</strong> include at least one embedded dot. That is,
-    <code>.example.com</code> is legal, but <code>www.example.com</code> and 
+    <code>.example.com</code> is legal, but <code>www.example.com</code> and
     <code>.com</code> are not.</p>
 
     <note>Most browsers in use today will not allow cookies to be set
-    for a two-part top level domain, such as <code>.co.uk</code>, 
+    for a two-part top level domain, such as <code>.co.uk</code>,
     although such a domain ostensibly fulfills the requirements
-    above.<br /> 
-    
+    above.<br />
+
     These domains are equivalent to top level domains such as
     <code>.com</code>, and allowing such cookies may be a security
     risk. Thus, if you are under a two-part top level domain, you
     should still use your actual domain, as you would with any other top
     level domain (for example <code>.example.co.uk</code>).
-    </note> 
+    </note>
 
     <example>
     CookieDomain .example.com
@@ -212,7 +212,7 @@
     user-tracking cookie for all new requests. This directive can
     be used to turn this behavior on or off on a per-server or
     per-directory basis. By default, enabling
-    <module>mod_usertrack</module> will <strong>not</strong> 
+    <module>mod_usertrack</module> will <strong>not</strong>
     activate cookies. </p>
 
     <example>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_version.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_version.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_version.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_version.xml Fri Sep 23 13:36:39 2011
@@ -97,8 +97,8 @@
       &lt;/IfVersion&gt;
     </example>
 
-    <p>Besides the numerical comparison it is possible to match a 
-    <glossary ref="regex">regular expression</glossary> 
+    <p>Besides the numerical comparison it is possible to match a
+    <glossary ref="regex">regular expression</glossary>
     against the httpd version. There are two ways to write it:</p>
 
     <table style="zebra" border="1">

Modified: httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_vhost_alias.xml Fri Sep 23 13:36:39 2011
@@ -35,7 +35,7 @@ hosting</description>
     the HTTP request to be used as part of the pathname to
     determine what files to serve. This allows for easy use of a
     huge number of virtual hosts with similar configurations.</p>
-    
+
     <note><title>Note</title>
       <p>If <module>mod_alias</module> or <module>mod_userdir</module> are
       used for translating URIs to filenames, they will override the
@@ -52,7 +52,7 @@ hosting</description>
 </summary>
 
 <seealso><directive module="core">UseCanonicalName</directive></seealso>
-<seealso><a href="../vhosts/mass.html">Dynamically configured mass 
+<seealso><a href="../vhosts/mass.html">Dynamically configured mass
     virtual hosting</a></seealso>
 
 <section id="interpol">
@@ -77,7 +77,7 @@ hosting</description>
 
 <tr><td><code>%N.M</code></td>
 <td>insert (part of) the name</td></tr>
-     
+
 </table>
 
     <p><code>N</code> and <code>M</code> are used to specify
@@ -135,7 +135,7 @@ hosting</description>
     <code>http://www.example.com/directory/file.html</code> will be
     satisfied by the file
     <code>/usr/local/apache/vhosts/www.example.com/directory/file.html</code>.
-    </p> 
+    </p>
 
     <p>For a very large number of virtual hosts it is a good idea
     to arrange the files to reduce the size of the
@@ -203,7 +203,7 @@ hosting</description>
     <code>http://www.domain.example.com/directory/file.html</code>
     will be satisfied by the file
     <code>/usr/local/apache/vhosts/domain.example/directory/file.html</code>.</p>
-     
+
     <p>The <directive module="mod_log_config">LogFormat</directive>
     directives <code>%V</code> and <code>%A</code> are useful
     in conjunction with this module.</p>
@@ -227,9 +227,9 @@ for a given virtual host</description>
     value of the server name. The result of expanding
     <em>interpolated-directory</em> is used as the root of the
     document tree in a similar manner to the <directive
-    module="core">DocumentRoot</directive> directive's argument. 
+    module="core">DocumentRoot</directive> directive's argument.
     If <em>interpolated-directory</em> is <code>none</code> then
-    <directive>VirtualDocumentRoot</directive> is turned off. This directive 
+    <directive>VirtualDocumentRoot</directive> is turned off. This directive
     cannot be used in the same context as <directive
     module="mod_vhost_alias">VirtualDocumentRootIP</directive>.</p>
 

Modified: httpd/httpd/trunk/docs/manual/mod/mpm_common.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mpm_common.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mpm_common.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mpm_common.xml Fri Sep 23 13:36:39 2011
@@ -40,16 +40,16 @@ switch before dumping core</description>
 <usage>
     <p>This controls the directory to which Apache httpd attempts to
     switch before dumping core. If your operating system is configured to
-    create core files in the working directory of the crashing process, 
+    create core files in the working directory of the crashing process,
     <directive>CoreDumpDirectory</directive> is necessary to change working
-    directory from the default <directive module="core">ServerRoot</directive> 
+    directory from the default <directive module="core">ServerRoot</directive>
     directory, which should not be writable by the user the server runs as.</p>
 
-    <p>If you want a core dump for debugging, you can use this directive to 
+    <p>If you want a core dump for debugging, you can use this directive to
     place it in a different location. This directive has no effect if your
     operating system is not configured to write core files to the working directory
     of the crashing processes.</p>
-    
+
     <note><title>Core Dumps on Linux</title>
       <p>If Apache httpd starts as root and switches to another user, the
       Linux kernel <em>disables</em> core dumps even if the directory is
@@ -66,8 +66,8 @@ switch before dumping core</description>
     </note>
 
     <note><title>Specific signals</title>
-      <p><directive>CoreDumpDirectory</directive> processing only occurs for 
-      a select set of fatal signals: SIGFPE, SIGILL, SIGABORT, 
+      <p><directive>CoreDumpDirectory</directive> processing only occurs for
+      a select set of fatal signals: SIGFPE, SIGILL, SIGABORT,
       SIGSEGV, and SIGBUS.</p>
       <p>On some operating systems, SIGQUIT also results in a core dump but
       does not go through <directive>CoreDumpDirectory</directive> or
@@ -95,7 +95,7 @@ after a crash</description>
     configured with the <code>--enable-exception-hook</code> option. It
     enables a hook that allows external modules to plug in and do something
     after a child crashed.</p>
-    
+
     <p>There are already two modules, <code>mod_whatkilledus</code> and
     <code>mod_backtrace</code> that make use of this hook. Please have a
     look at Jeff Trawick's <a
@@ -117,7 +117,7 @@ will exit.</description>
 
 <usage>
     <p>The <directive>GracefulShutdownTimeout</directive> specifies
-    how many seconds after receiving a "graceful-stop" signal, a 
+    how many seconds after receiving a "graceful-stop" signal, a
     server should continue to run, handling the existing connections.</p>
 
     <p>Setting this value to zero means that the server will wait
@@ -222,14 +222,14 @@ The <var>protocol</var> argument was add
       Listen [2001:db8::a00:20ff:fea7:ccea]:80
     </example>
 
-    <p>The optional <var>protocol</var> argument is not required for most 
-       configurations. If not specified, <code>https</code> is the default for 
-       port 443 and <code>http</code> the default for all other ports.  The 
+    <p>The optional <var>protocol</var> argument is not required for most
+       configurations. If not specified, <code>https</code> is the default for
+       port 443 and <code>http</code> the default for all other ports.  The
        protocol is used to determine which module should handle a request, and
-       to apply protocol specific optimizations with the 
+       to apply protocol specific optimizations with the
        <directive module="core">AcceptFilter</directive> directive.</p>
 
-    <p>You only need to set the protocol if you are running on non-standard 
+    <p>You only need to set the protocol if you are running on non-standard
        ports.  For example, running an <code>https</code> site on port 8443:</p>
 
     <example>
@@ -381,7 +381,7 @@ will handle during its life</description
     <p>Maximum number of idle threads. Different MPMs deal with this
     directive differently.</p>
 
-    <p>For <module>worker</module>, the default is 
+    <p>For <module>worker</module>, the default is
     <code>MaxSpareThreads 250</code>. This MPM deals with idle threads
     on a server-wide basis. If there are too many idle threads in the
     server then child processes are killed until the number of idle
@@ -515,7 +515,7 @@ Apache HTTP Server</a></seealso>
 <usage>
     <p>Sets the server's TCP send buffer size to the number of bytes
     specified. It is often useful to set this past the OS's standard
-    default value on high speed, high latency conections 
+    default value on high speed, high latency conections
     (<em>i.e.</em>, 100ms or so, such as transcontinental fast pipes).</p>
 
     <p>If set to the value of <code>0</code>, the server will use the
@@ -611,7 +611,7 @@ Apache HTTP Server</a></seealso>
     there is usually little reason to adjust this parameter.</p>
 
     <p>The default value differs from MPM to MPM. <module>worker</module>
-    defaults to <code>StartServers 3</code>; <module>prefork</module> 
+    defaults to <code>StartServers 3</code>; <module>prefork</module>
     defaults to <code>5</code>; <module>mpmt_os2</module> defaults to
     <code>2</code>.</p>
 </usage>
@@ -717,8 +717,8 @@ and later</compatibility>
 
 <directivesynopsis>
 <name>ThreadStackSize</name>
-<description>The size in bytes of the stack used by threads handling 
-client connections</description> 
+<description>The size in bytes of the stack used by threads handling
+client connections</description>
 <syntax>ThreadStackSize <var>size</var></syntax>
 <default>65536 on NetWare; varies on other operating systems</default>
 <contextlist><context>server config</context></contextlist>
@@ -729,11 +729,11 @@ client connections</description> 
 <compatibility>Available in Apache HTTP Server 2.1 and later</compatibility>
 
 <usage>
-    <p>The <directive>ThreadStackSize</directive> directive sets the 
+    <p>The <directive>ThreadStackSize</directive> directive sets the
     size of the stack (for autodata) of threads which handle client
-    connections and call modules to help process those connections.  
-    In most cases the operating system default for stack size is 
-    reasonable, but there are some conditions where it may need to be 
+    connections and call modules to help process those connections.
+    In most cases the operating system default for stack size is
+    reasonable, but there are some conditions where it may need to be
     adjusted:</p>
 
     <ul>
@@ -742,13 +742,13 @@ client connections</description> 
       which use a relatively large amount of autodata storage.  Those
       same modules may have worked fine on other platforms where the
       default thread stack size is larger.  This type of crash is
-      resolved by setting <directive>ThreadStackSize</directive> to a 
-      value higher than the operating system default.  This type of 
-      adjustment is necessary only if the provider of the third-party 
+      resolved by setting <directive>ThreadStackSize</directive> to a
+      value higher than the operating system default.  This type of
+      adjustment is necessary only if the provider of the third-party
       module specifies that it is required, or if diagnosis of an Apache httpd
       crash indicates that the thread stack size was too small.</li>
 
-      <li>On platforms where the default thread stack size is 
+      <li>On platforms where the default thread stack size is
       significantly larger than necessary for the web server
       configuration, a higher number of threads per child process
       will be achievable if <directive>ThreadStackSize</directive> is
@@ -761,9 +761,9 @@ client connections</description> 
       the current <directive>ThreadStackSize</directive> setting.</li>
 
       <li>On Linux, this directive can only be used to increase the default
-      stack size, as the underlying system call uses the value as a 
-      <em>minimum</em> stack size.  The (often large) soft limit for 
-      <code>ulimit -s</code> (8MB if unlimited) is used as the default stack 
+      stack size, as the underlying system call uses the value as a
+      <em>minimum</em> stack size.  The (often large) soft limit for
+      <code>ulimit -s</code> (8MB if unlimited) is used as the default stack
       size.</li>
     </ul>
 

Modified: httpd/httpd/trunk/docs/manual/mod/mpmt_os2.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mpmt_os2.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mpmt_os2.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mpmt_os2.xml Fri Sep 23 13:36:39 2011
@@ -36,7 +36,7 @@
     involves spawning children as required to ensure there are always
     <directive module="mpm_common">StartServers</directive> processes
     accepting connections.</p>
-    
+
     <p>Each child process consists of a a pool of worker threads and a
     main thread that accepts connections and passes them to the workers via
     a work queue. The worker thread pool is dynamic, managed by a

Modified: httpd/httpd/trunk/docs/manual/mod/worker.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/worker.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/worker.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/worker.xml Fri Sep 23 13:36:39 2011
@@ -46,9 +46,9 @@
 <seealso><a href="../bind.html">Setting which addresses and ports Apache HTTP Server uses</a></seealso>
 
 <section id="how-it-works"><title>How it Works</title>
-    <p>A single control process (the parent) is responsible for launching 
+    <p>A single control process (the parent) is responsible for launching
     child processes. Each child process creates a fixed number of server
-    threads as specified in the <directive 
+    threads as specified in the <directive
     module="mpm_common">ThreadsPerChild</directive> directive, as well
     as a listener thread which listens for connections and passes them
     to a server thread for processing when they arrive.</p>
@@ -76,25 +76,25 @@
 
     <p>Two directives set hard limits on the number of active child
     processes and the number of server threads in a child process,
-    and can only be changed by fully stopping the server and then 
+    and can only be changed by fully stopping the server and then
     starting it again.  <directive module="mpm_common">ServerLimit
-    </directive> is a hard limit on the number of active child 
-    processes, and must be greater than or equal to the 
+    </directive> is a hard limit on the number of active child
+    processes, and must be greater than or equal to the
     <directive module="mpm_common">MaxRequestWorkers</directive>
     directive divided by the <directive module="mpm_common">
-    ThreadsPerChild</directive> directive.  
+    ThreadsPerChild</directive> directive.
     <directive module="mpm_common">ThreadLimit</directive> is a hard
     limit of the number of server threads, and must be greater than
-    or equal to the <directive 
+    or equal to the <directive
     module="mpm_common">ThreadsPerChild</directive> directive.</p>
 
-    <p>In addition to the set of active child processes, there may 
+    <p>In addition to the set of active child processes, there may
     be additional child processes which are terminating, but where at
     least one server thread is still handling an existing client
-    connection.  Up to <directive 
-    module="mpm_common">MaxRequestWorkers</directive> terminating processes 
-    may be present, though the actual number can be expected to be 
-    much smaller.  This behavior can be avoided by disabling the 
+    connection.  Up to <directive
+    module="mpm_common">MaxRequestWorkers</directive> terminating processes
+    may be present, though the actual number can be expected to be
+    much smaller.  This behavior can be avoided by disabling the
     termination of individual child processes, which is achieved using
     the following:</p>
 

Modified: httpd/httpd/trunk/docs/manual/mpm.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mpm.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mpm.xml (original)
+++ httpd/httpd/trunk/docs/manual/mpm.xml Fri Sep 23 13:36:39 2011
@@ -62,7 +62,7 @@ how they are used by the Apache HTTP Ser
 
       <li>The server can be better customized for the needs of the
       particular site. For example, sites that need a great deal of
-      scalability can choose to use a threaded MPM like 
+      scalability can choose to use a threaded MPM like
       <module>worker</module> or <module>event</module>, while sites requiring
       stability or compatibility with older software can use a
       <module>prefork</module>.</li>
@@ -85,7 +85,7 @@ choice at compile-time.</p>
 <columnspec><column width=".2"/><column width=".2"/></columnspec>
 <tr><td>Netware</td><td><module>mpm_netware</module></td></tr>
 <tr><td>OS/2</td><td><module>mpmt_os2</module></td></tr>
-<tr><td>Unix</td><td><module>prefork</module>, <module>worker</module>, or 
+<tr><td>Unix</td><td><module>prefork</module>, <module>worker</module>, or
     <module>event</module>, depending on platform capabilities</td></tr>
 <tr><td>Windows</td><td><module>mpm_winnt</module></td></tr>
 </table>
@@ -113,7 +113,7 @@ choice at compile-time.</p>
     <p>On Unix and similar platforms, MPMs can be built as DSO modules and
     dynamically loaded into the server in the same manner as other DSO
     modules.  Building MPMs as DSO modules allows the MPM to be changed by
-    updating the <directive module="mod_so">LoadModule</directive> directive 
+    updating the <directive module="mod_so">LoadModule</directive> directive
     for the MPM instead of by rebuilding the server.</p>
 
     <p>This feature is enabled using the

Modified: httpd/httpd/trunk/docs/manual/new_features_2_4.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/new_features_2_4.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/new_features_2_4.xml (original)
+++ httpd/httpd/trunk/docs/manual/new_features_2_4.xml Fri Sep 23 13:36:39 2011
@@ -38,11 +38,11 @@
       <dd>It is now possible to specify <directive module="core"
       >KeepAliveTimeout</directive> in milliseconds.
       </dd>
- 
+
       <dt>Loadable MPMs</dt>
-      <dd>Multiple MPMs can now be built as loadable modules at compile time.  
+      <dd>Multiple MPMs can now be built as loadable modules at compile time.
       The MPM of choice can be configured at run time.</dd>
- 
+
       <dt>Per-module and per-directory LogLevel configuration</dt>
       <dd>The <directive module="core">LogLevel</directive> can now be
       configured per module and per directory.  New levels <code>trace1</code>
@@ -51,13 +51,13 @@
 
       <dt>Event MPM</dt>
       <dd>The Event MPM is no longer experimental but is now fully supported.</dd>
- 
+
       <dt>Asynchronous support</dt>
       <dd>Better support for asynchronous read/write for supporting MPMs and
       platforms.</dd>
 
       <dt>Per-request configuration sections</dt>
-      <dd>&lt;<directive module="core">If</directive>&gt; sections can be used to 
+      <dd>&lt;<directive module="core">If</directive>&gt; sections can be used to
       set the configuration based on per-request criteria</dd>
 
       <dt>NameVirtualHost directive</dt>
@@ -80,7 +80,7 @@
       <dd>Convert response body into an RFC2397 data URL</dd>
 
       <dt><module>mod_lua</module></dt>
-      <dd>Embeds the <a href="http://www.lua.org/">Lua</a> language into httpd, 
+      <dd>Embeds the <a href="http://www.lua.org/">Lua</a> language into httpd,
       for configuration and small business logic functions.</dd>
 
       <dt><module>mod_proxy_express</module></dt>
@@ -129,14 +129,14 @@
       certificate.  The default responder is configurable, along with
       the decision on whether to prefer the responder designated in
       the client certificate itself.</dd>
-      
-      <dd><module>mod_ssl</module> now also supports OCSP stapling, where the 
-      server pro-actively obtains an OCSP verification of its certificate and 
+
+      <dd><module>mod_ssl</module> now also supports OCSP stapling, where the
+      server pro-actively obtains an OCSP verification of its certificate and
       transmits that to the client during the handshake. </dd>
-      
-      <dd><module>mod_ssl</module> can now be configured to share SSL Session 
+
+      <dd><module>mod_ssl</module> can now be configured to share SSL Session
       data between servers through memcached</dd>
- 
+
       <dt><module>mod_proxy</module></dt>
 
       <dd>The <directive module="mod_proxy">ProxyPass</directive> directive
@@ -182,7 +182,7 @@
 
       <dt><module>mod_cgi</module>, <module>mod_include</module>,
           <module>mod_isapi</module>, ...</dt>
-      <dd>Translation of headers to environment variables is more strict than 
+      <dd>Translation of headers to environment variables is more strict than
       before to mitigate some possible cross-site-scripting attacks via header
       injection. Headers containing invalid characters (including underscores)
       are now silently dropped. <a href="env.html">Environment Variables
@@ -252,7 +252,7 @@
           <module>mod_ssl</module>.</dd>
 
       <dt>Authorization Logic Containers</dt>
-      
+
       <dd>Authorization modules now register as a provider, via
       ap_register_auth_provider(), to support advanced authorization logic,
       such as <directive module="mod_authz_core" type="section"
@@ -268,7 +268,7 @@
       supported.</dd>
 
       <dt>Cache Status Hook Added</dt>
-      
+
       <dd>The <module>mod_cache</module> module now includes a new
       <code>cache_status</code> hook, which is called when the caching
       decision becomes known. A default implementation is provided

Modified: httpd/httpd/trunk/docs/manual/platform/netware.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/platform/netware.xml?rev=1174747&r1=1174746&r2=1174747&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/platform/netware.xml (original)
+++ httpd/httpd/trunk/docs/manual/platform/netware.xml Fri Sep 23 13:36:39 2011
@@ -54,9 +54,9 @@
 
     <title>Requirements</title>
 
-    <p>Apache 2.0 is designed to run on NetWare 6.0 service pack 3 
+    <p>Apache 2.0 is designed to run on NetWare 6.0 service pack 3
     and above. If you are running a service pack less
-    than SP3, you must install the latest 
+    than SP3, you must install the latest
     <a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries
     for C (LibC)</a>.</p>
 
@@ -66,7 +66,7 @@
     <p>Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment
     as long as the latest service pack or the latest version
     of the <a href="http://developer.novell.com/ndk/libc.htm">NetWare Libraries
-    for C (LibC)</a> has been installed .  <strong>WARNING:</strong> Apache 2.0 
+    for C (LibC)</a> has been installed .  <strong>WARNING:</strong> Apache 2.0
     for NetWare has not been targeted for or tested in this environment.</p>
 
   </section>
@@ -81,7 +81,7 @@
     will list the current release, any more recent alpha or
     beta-test releases, together with details of mirror web and
     anonymous ftp sites. Binary builds of the latest releases of
-    Apache 2.0 for NetWare can be downloaded from 
+    Apache 2.0 for NetWare can be downloaded from
     <a href="http://www.apache.org/dist/httpd/binaries/netware">here</a>.</p>
 
   </section>
@@ -91,7 +91,7 @@
     <title>Installing Apache for NetWare</title>
 
     <p>There is no Apache install program for NetWare currently. If you
-    are building Apache 2.0 for NetWare from source, you will need to 
+    are building Apache 2.0 for NetWare from source, you will need to
     copy the files over to the server manually.</p>
 
     <p>Follow these steps to install Apache on NetWare from the
@@ -127,7 +127,7 @@
       <li>Create a directory under <code>SYS:/APACHE2</code>
       called <code>BIN</code></li>
 
-      <li>Copy <code>HTDIGEST.NLM</code>, <code>HTPASSWD.NLM</code>, 
+      <li>Copy <code>HTDIGEST.NLM</code>, <code>HTPASSWD.NLM</code>,
       <code>HTDBM.NLM</code>, <code>LOGRES.NLM</code>, <code>ROTLOGS.NLM</code>
       to <code>SYS:/APACHE2/BIN</code></li>
 
@@ -138,7 +138,7 @@
       <code>SYS:/APACHE2/CONF</code> directory and rename to
       <code>HTTPD.CONF</code></li>
 
-      <li>Copy the <code>MIME.TYPES</code>, <code>CHARSET.CONV</code> and 
+      <li>Copy the <code>MIME.TYPES</code>, <code>CHARSET.CONV</code> and
       <code>MAGIC</code> files to <code>SYS:/APACHE2/CONF</code> directory</li>
 
       <li>Copy all files and subdirectories in <code>\HTTPD-2.0\DOCS\ICONS</code>
@@ -174,9 +174,9 @@
     <p>Apache may be installed to other volumes besides the default <code>SYS</code> volume.</p>
 
     <p>During the build process, adding the keyword "install" to the makefile command line
-    will automatically produce a complete distribution package under the subdirectory 
-    <code>DIST</code>. Install Apache by simply copying the distribution that was produced 
-    by the makfiles to the root of a NetWare volume (see: <a href="#comp">Compiling Apache for 
+    will automatically produce a complete distribution package under the subdirectory
+    <code>DIST</code>. Install Apache by simply copying the distribution that was produced
+    by the makfiles to the root of a NetWare volume (see: <a href="#comp">Compiling Apache for
     NetWare</a> below).</p>
 
   </section>
@@ -277,7 +277,7 @@
 
     <p>Apache 2.0 for NetWare includes a set of command line directives that can
     be used to modify or display information about the running instance of the
-    web server. These directives are only available while Apache is running. Each 
+    web server. These directives are only available while Apache is running. Each
     of these directives must be preceded by the keyword <code>APACHE2</code>.</p>
 
     <dl>
@@ -299,7 +299,7 @@
 
       <dt>SETTINGS</dt>
       <dd>Enables or disables the thread status display
-      on the console. When enabled, the state of each running threads is displayed 
+      on the console. When enabled, the state of each running threads is displayed
       on the Apache console screen.</dd>
 
       <dt>SHUTDOWN</dt>
@@ -322,7 +322,7 @@
     <title>Configuring Apache for NetWare</title>
 
     <p>Apache is configured by reading configuration files usually stored
-    in the <code>conf</code> directory. These are the same as files used 
+    in the <code>conf</code> directory. These are the same as files used
     to configure the Unix version, but there are a few different directives for
     Apache on NetWare. See the <a href="../">Apache
     documentation</a> for all the available directives.</p>
@@ -370,11 +370,11 @@
       </li>
 
       <li>
-        <p>The directives that accept filenames as arguments must use 
-        NetWare filenames instead of Unix names. However, because Apache 
-        uses Unix-style names internally, forward slashes must be used 
-        rather than backslashes. It is recommended that all rooted file paths 
-        begin with a volume name. If omitted, Apache will assume the 
+        <p>The directives that accept filenames as arguments must use
+        NetWare filenames instead of Unix names. However, because Apache
+        uses Unix-style names internally, forward slashes must be used
+        rather than backslashes. It is recommended that all rooted file paths
+        begin with a volume name. If omitted, Apache will assume the
         <code>SYS:</code> volume which may not be correct.</p>
       </li>
 
@@ -427,8 +427,8 @@
 
     <title>Compiling Apache for NetWare</title>
 
-    <p>Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once 
-    Apache has been built, it can be installed to the root of any NetWare 
+    <p>Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once
+    Apache has been built, it can be installed to the root of any NetWare
     volume. The default is the <code>sys:/Apache2</code> directory.</p>
 
     <p>Before running the server you must fill out the <code>conf</code>
@@ -497,7 +497,7 @@
         for example:
         <example>Set ZLIBSDK=D:\NOVELL\zlib</example>
         </li>
-        
+
         <li>Set the environment variable <code>PCRESDK</code> to the location
         where you installed the source code for the PCRE Library, for example:
         <example>Set PCRESDK=D:\NOVELL\pcre</example>
@@ -529,11 +529,11 @@
 
         <li>Change directory to <code>\httpd-2.0</code> and build the prebuild utilities
         by running "<code>gmake -f nwgnumakefile prebuild</code>". This target will create
-        the directory <code>\httpd-2.0\nwprebuild</code> and copy each of the utilities 
+        the directory <code>\httpd-2.0\nwprebuild</code> and copy each of the utilities
         to this location that are necessary to complete the following build steps.
         </li>
 
-        <li>Copy the files <code>\httpd-2.0\nwprebuild\GENCHARS.nlm</code> and 
+        <li>Copy the files <code>\httpd-2.0\nwprebuild\GENCHARS.nlm</code> and
         <code>\httpd-2.0\nwprebuild\DFTABLES.nlm</code> to the <code>SYS:</code> volume of a
         NetWare server and run them using the following commands:
           <example>
@@ -591,7 +591,7 @@
       <title>Additional environment variable options</title>
 
       <ul>
-        <li>To build all of the experimental modules, set the environment 
+        <li>To build all of the experimental modules, set the environment
         variable <code>EXPERIMENTAL</code>:
         <example>Set EXPERIMENTAL=1</example>
         </li>
@@ -609,14 +609,14 @@
 
       <title>Building mod_ssl for the NetWare platform</title>
 
-      <p>By default Apache for NetWare uses the built-in module 
+      <p>By default Apache for NetWare uses the built-in module
       <module>mod_nw_ssl</module> to provide SSL services.  This module
       simply enables the native SSL services implemented in NetWare OS
       to handle all encryption for a given port.  Alternatively, mod_ssl
       can also be used in the same manner as on other platforms.</p>
 
       <p>Before mod_ssl can be built for the NetWare platform, the OpenSSL
-      libraries must be provided.  This can be done through the following 
+      libraries must be provided.  This can be done through the following
       steps:</p>
 
       <ul>
@@ -625,8 +625,8 @@
           page (older 0.9.7 versions need to be patched and are therefore not
           recommended).</li>
 
-          <li>Edit the file <code>NetWare/set_env.bat</code> and modify any 
-          tools and utilities paths so that they correspond to your build 
+          <li>Edit the file <code>NetWare/set_env.bat</code> and modify any
+          tools and utilities paths so that they correspond to your build
           environment.</li>
 
           <li>From the root of the OpenSSL source directory, run the following
@@ -637,7 +637,7 @@
           </example>
           For performance reasons you should enable to build with ASM code.
           Download NASM from the <a href="http://nasm.sourceforge.net/">SF site</a>.
-          Then configure OpenSSL to use ASM code: 
+          Then configure OpenSSL to use ASM code:
           <example>
               Netware\build netware-libc nw-nasm enable-mdc2 enable-md5
           </example>



Mime
View raw message