[deployment-guide/comm-rel: 602/727] Removed the most of the index terms.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 13:16:10 UTC 2010
commit b1d3e9860ccf0222feea3050c93ed6392eb5a9b0
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon Sep 6 18:46:32 2010 +0200
Removed the most of the index terms.
I am going to index this chapter from scratch anyway.
en-US/The_Apache_HTTP_Server.xml | 261 --------------------------------------
1 files changed, 0 insertions(+), 261 deletions(-)
---
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index 8121a6c..6764f80 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -30,46 +30,21 @@
<itemizedlist>
<listitem>
<para>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary>features</secondary>
- <tertiary>improved caching modules</tertiary>
- </indexterm>
Improved caching modules, that is, <systemitem class="resource">mod_cache</systemitem> and <systemitem class="resource">mod_disk_cache</systemitem>.
</para>
</listitem>
<listitem>
<para>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary>features</secondary>
- <tertiary>proxy load balancing</tertiary>
- </indexterm>
Support for proxy load balancing, that is, the <systemitem class="resource">mod_proxy_balancer</systemitem> module.
</para>
</listitem>
<listitem>
<para>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary>features</secondary>
- <tertiary>large files support</tertiary>
- </indexterm>
Support for large files on 32-bit architectures, allowing the web server to handle files greater than 2GB.
</para>
</listitem>
<listitem>
<para>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary>features</secondary>
- <tertiary>improved authentication support</tertiary>
- </indexterm>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary>features</secondary>
- <tertiary>improved authorization support</tertiary>
- </indexterm>
A new structure for authentication and authorization support, replacing the authentication modules provided in previous versions.
</para>
</listitem>
@@ -96,27 +71,8 @@
</section>
<section id="s1-httpd-mig">
<title>Migrating Apache HTTP Server Configuration Files</title>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>2.2</secondary>
- <tertiary>2.0</tertiary>
- </indexterm>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>2.2</secondary>
- <tertiary>migration to 2.2</tertiary>
- </indexterm>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>migration to 2.2</secondary>
- </indexterm>
<section id="s1-httpd-v22-mig">
<title>Migrating Apache HTTP Server 2.0 Configuration Files</title>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>2.2</secondary>
- <tertiary>migration from 2.0</tertiary>
- </indexterm>
<para>
This section outlines migration from version 2.0 to 2.2. <!-- If you are migrating from version 1.3, please refer to <xref linkend="s3-httpd-v2-mig" />. -->
</para>
@@ -149,31 +105,16 @@
</section>
<section id="s1-apache-startstop">
<title>Running the <systemitem class="service">httpd</systemitem> Service</title>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary><systemitem class="service">httpd</systemitem> service</secondary>
- <tertiary>running</tertiary>
- </indexterm>
<para>
To run the <systemitem class="service">httpd</systemitem> service, type the following at a shell prompt:
</para>
<screen>~]# <command>service httpd start</command>
Starting httpd: [ OK ]</screen>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary><systemitem class="service">httpd</systemitem> service</secondary>
- <tertiary>stopping</tertiary>
- </indexterm>
<para>
Similarly, to stop the running service, type:
</para>
<screen>~]# <command>service httpd stop</command>
Stopping httpd: [ OK ]</screen>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary><systemitem class="service">httpd</systemitem> service</secondary>
- <tertiary>enabling</tertiary>
- </indexterm>
<para>
Finally, if you want the service to start automatically at the boot time, use the following command:
</para>
@@ -181,11 +122,6 @@ Stopping httpd: [ OK ]</screen>
<para>
This will enable the service for all runlevels. Refer to <xref linkend="ch-Controlling_Access_to_Services" /> for the detailed information on how to manage services.
</para>
- <indexterm>
- <primary><application>Apache HTTP Server</application></primary>
- <secondary><systemitem class="service">httpd</systemitem> service</secondary>
- <tertiary>checking the status</tertiary>
- </indexterm>
<para>
Note that you can check whether the service is running by typing the following:
</para>
@@ -2608,14 +2544,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<formalpara id="s3-apache-setenvif">
<title>SetEnvIf</title>
- <indexterm>
- <primary><command>SetEnvIf</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>SetEnvIf</command></secondary>
- </indexterm>
<para>
<command>SetEnvIf</command> sets environment variables based on the headers of incoming connections. It is <emphasis>not</emphasis> solely an SSL directive, though it is present in the supplied <filename>/etc/httpd/conf.d/ssl.conf</filename> file. It's purpose in this context is to disable HTTP keepalive and to allow SSL to close the connection without a closing notification from the client browser. This setting is necessary for certain browsers that do not reliably shut down the SSL connection.
</para>
@@ -2644,11 +2572,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s2-apache-mpm-containers">
<title>MPM Specific Server-Pool Directives</title>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>2.0</secondary>
- <tertiary>MPM specific directives</tertiary>
- </indexterm>
<para>
<!-- As explained in <xref linkend="s3-httpd-v2-mig-pool" />, --> The responsibility for managing characteristics of the server-pool falls to a module group called MPMs under Apache HTTP Server 2.0. The characteristics of the server-pool differ depending upon which MPM is used. For this reason, an <command>IfModule</command> container is necessary to define the server-pool for the MPM in use.
</para>
@@ -2660,50 +2583,18 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<formalpara id="s3-apache-maxclients">
<title>MaxClients</title>
- <indexterm>
- <primary><command>MaxClients</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MaxClients</command></secondary>
- </indexterm>
<para>
<command>MaxClients</command> sets a limit on the total number of server processes, or simultaneously connected clients, that can run at one time. The main purpose of this directive is to keep a runaway Apache HTTP Server from crashing the operating system. For busy servers this value should be set to a high value. The server's default is set to 150 regardless of the MPM in use. However, it is not recommended that the value for <command>MaxClients</command> exceeds <command>256</command> when using the <command>prefork</command> MPM.
</para>
</formalpara>
<formalpara id="s3-apache-maxrequestsperchild">
<title>MaxRequestsPerChild</title>
- <indexterm>
- <primary><command>MaxRequestsPerChild</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MaxRequestsPerChild</command></secondary>
- </indexterm>
<para>
<command>MaxRequestsPerChild</command> sets the total number of requests each child server process serves before the child dies. The main reason for setting <command>MaxRequestsPerChild</command> is to avoid long-lived process induced memory leaks. The default <command>MaxRequestsPerChild</command> for the <command>prefork</command> MPM is <command>4000</command> and for the <command>worker</command> MPM is <command>0</command>.
</para>
</formalpara>
<formalpara id="s3-apache-minmaxspareservers">
<title>MinSpareServers and MaxSpareServers</title>
- <indexterm>
- <primary><command>MinSpareServers</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MinSpareServers</command></secondary>
- </indexterm>
- <indexterm>
- <primary><command>MaxSpareServers</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MaxSpareServers</command></secondary>
- </indexterm>
<para>
These values are only used with the <command>prefork</command> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server processes based on the number of incoming requests. The server checks the number of servers waiting for a request and kills some if there are more than <command>MaxSpareServers</command> or creates some if the number of servers is less than <command>MinSpareServers</command>.
</para>
@@ -2713,22 +2604,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<formalpara id="s3-apache-minmaxsparethreads">
<title>MinSpareThreads and MaxSpareThreads</title>
- <indexterm>
- <primary><command>MinSpareThreads</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MinSpareThreads</command></secondary>
- </indexterm>
- <indexterm>
- <primary><command>MaxSpareThreads</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>MaxSpareThreads</command></secondary>
- </indexterm>
<para>
These values are only used with the <command>worker</command> MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server threads based on the number of incoming requests. The server checks the number of server threads waiting for a request and kills some if there are more than <command>MaxSpareThreads</command> or creates some if the number of servers is less than <command>MinSpareThreads</command>.
</para>
@@ -2738,28 +2613,12 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<formalpara id="s3-apache-startservers">
<title>StartServers</title>
- <indexterm>
- <primary><command>StartServers</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>StartServers</command></secondary>
- </indexterm>
<para>
The <command>StartServers</command> directive sets how many server processes are created upon startup. Since the Web server dynamically kills and creates server processes based on traffic load, it is not necessary to change this parameter. The Web server is set to start <command>8</command> server processes at startup for the <command>prefork</command> MPM and <command>2</command> for the <command>worker</command> MPM.
</para>
</formalpara>
<formalpara id="s3-apache-threadsperchild">
<title>ThreadsPerChild</title>
- <indexterm>
- <primary><command>ThreadsPerChild</command></primary>
- <secondary>Apache configuration directive</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration directives, Apache</primary>
- <secondary><command>ThreadsPerChild</command></secondary>
- </indexterm>
<para>
This value is only used with the <command>worker</command> MPM. It sets the number of threads within each child process. The default value for this directive is <command>25</command>.
</para>
@@ -2768,27 +2627,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s1-apache-addmods">
<title>Adding Modules</title>
- <indexterm>
- <primary>modules</primary>
- <secondary>Apache</secondary>
- <tertiary>loading</tertiary>
- </indexterm>
- <indexterm>
- <primary>DSOs</primary>
- <secondary>loading</secondary>
- </indexterm>
- <indexterm>
- <primary>objects, dynamically shared</primary>
- <see>DSOs</see>
- </indexterm>
- <indexterm>
- <primary>APXS Apache utility</primary>
- </indexterm>
- <indexterm>
- <primary>modules</primary>
- <secondary>Apache</secondary>
- <tertiary>the own</tertiary>
- </indexterm>
<para>
The Apache HTTP Server is distributed with a number of modules. More information about Apache HTTP modules can be found on <ulink url="http://httpd.apache.org/docs/2.2/mod/" />.
</para>
@@ -2820,30 +2658,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s1-apache-virtualhosts">
<title>Virtual Hosts</title>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>running without security</secondary>
- </indexterm>
- <indexterm>
- <primary>security</primary>
- <secondary>running Apache without</secondary>
- </indexterm>
- <indexterm>
- <primary>virtual hosts</primary>
- <secondary>configuring</secondary>
- </indexterm>
- <indexterm>
- <primary>configuration</primary>
- <secondary>virtual hosts</secondary>
- </indexterm>
- <indexterm>
- <primary><command>DocumentRoot</command></primary>
- <secondary>changing</secondary>
- </indexterm>
- <indexterm>
- <primary>virtual hosts</primary>
- <secondary>name-based</secondary>
- </indexterm>
<para>
The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, hostname, or port is being requested. A complete guide to using virtual hosts is available online at <ulink url="http://httpd.apache.org/docs/2.2/vhosts/" />.
</para>
@@ -2882,10 +2696,6 @@ ErrorDocument 404 /404-not_found.html</screen>
<para>
The <command><VirtualHost></command> container is highly customizable and accepts almost every directive available within the main server configuration.
</para>
- <indexterm>
- <primary>virtual hosts</primary>
- <secondary><command>Listen</command> command</secondary>
- </indexterm>
<note>
<title>Tip</title>
<para>
@@ -2902,10 +2712,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s1-httpd-secure-server">
<title>Apache HTTP Secure Server Configuration</title>
- <indexterm>
- <primary>secure server</primary>
- <secondary>installing</secondary>
- </indexterm>
<para>
This section provides basic information on the Apache HTTP Server with the <filename>mod_ssl</filename> security module enabled to use the OpenSSL library and toolkit. The combination of these three components are referred to in this section as the secure Web server or just as the secure server.
</para>
@@ -2923,10 +2729,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<section id="s2-secureserver-optionalpackages">
<title>An Overview of Security-Related Packages</title>
- <indexterm>
- <primary>secure server</primary>
- <secondary>packages</secondary>
- </indexterm>
<para>
To enable the secure server, you must have the following packages installed at a minimum:
</para>
@@ -2962,23 +2764,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s2-secureserver-overview-certs">
<title>An Overview of Certificates and Security</title>
- <indexterm>
- <primary>Apache HTTP Server</primary>
- <secondary>securing</secondary>
- </indexterm>
- <indexterm>
- <primary>secure server</primary>
- <secondary>providing a certificate for</secondary>
- </indexterm>
- <indexterm>
- <primary>secure server</primary>
- <secondary>explanation of security</secondary>
- </indexterm>
- <indexterm>
- <primary>secure server</primary>
- <secondary>security</secondary>
- <tertiary>explanation of</tertiary>
- </indexterm>
<para>
Your secure server provides security using a combination of the Secure Sockets Layer (SSL) protocol and (in most cases) a digital certificate from a Certificate Authority (CA). SSL handles the encrypted communications as well as the mutual authentication between browsers and your secure server. The CA-approved digital certificate provides authentication for your secure server (the CA puts its reputation behind its certification of your organization's identity). When your browser is communicating using SSL encryption, the <computeroutput>https://</computeroutput> prefix is used at the beginning of the Uniform Resource Locator (URL) in the navigation bar.
</para>
@@ -3000,11 +2785,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s1-secureserver-oldcert">
<title>Using Pre-Existing Keys and Certificates</title>
- <indexterm>
- <primary>secure server</primary>
- <secondary>certificate</secondary>
- <tertiary>pre-existing</tertiary>
- </indexterm>
<para>
If you already have an existing key and certificate (for example, if you are installing the secure server to replace another company's secure server product), you can probably use your existing key and certificate with the secure server. The following two situations provide instances where you are not able to use your existing key and certificate:
</para>
@@ -3016,10 +2796,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</listitem>
<listitem>
<para>
- <indexterm>
- <primary>VeriSign</primary>
- <secondary>using existing certificate</secondary>
- </indexterm>
<emphasis>If you have a certificate from VeriSign and you are changing your server software</emphasis> — VeriSign is a widely used CA. If you already have a VeriSign certificate for another purpose, you may have been considering using your existing VeriSign certificate with your new secure server. However, you are not be allowed to because VeriSign issues certificates for one specific server software and IP address/domain name combination.
</para>
<para>
@@ -3039,15 +2815,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</para>
<screen><filename>/etc/pki/tls/certs/server.crt</filename></screen>
<para>
- <indexterm>
- <primary>secure server</primary>
- <secondary>upgrading from</secondary>
- </indexterm>
- <indexterm>
- <primary>secure server</primary>
- <secondary>certificate</secondary>
- <tertiary> moving it after an upgrade</tertiary>
- </indexterm>
If you are upgrading from the Red Hat Secure Web Server, your old key (<filename>httpsd.key</filename>) and certificate (<filename>httpsd.crt</filename>) are located in <filename>/etc/httpd/conf/</filename>. Move and rename your key and certificate so that the secure server can use them. Use the following two commands to move and rename your key and certificate files:
</para>
<screen><command>mv /etc/httpd/conf/httpsd.key /etc/pki/tls/private/server.key mv /etc/httpd/conf/httpsd.crt /etc/pki/tls/certs/server.crt</command></screen>
@@ -3058,11 +2825,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s2-secureserver-certs">
<title>Types of Certificates</title>
- <indexterm>
- <primary>secure server</primary>
- <secondary>certificate</secondary>
- <tertiary>test vs. signed vs. self-signed</tertiary>
- </indexterm>
<para>
If you installed your secure server from the RPM package provided by Red Hat, a randomly generated private key and a test certificate are generated and put into the appropriate directories. Before you begin using your secure server, however, you must generate your own key and obtain a certificate which correctly identifies your server.
</para>
@@ -3109,20 +2871,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</listitem>
<listitem>
<para>
- <indexterm>
- <primary>secure server</primary>
- <secondary>certificate</secondary>
- <tertiary>authorities</tertiary>
- </indexterm>
- <indexterm>
- <primary>CA</primary>
- <see>secure server</see>
- </indexterm>
- <indexterm>
- <primary>secure server</primary>
- <secondary>certificate</secondary>
- <tertiary>choosing a CA</tertiary>
- </indexterm>
Send the certificate request, along with documents proving your identity, to a CA. Red Hat does not make recommendations on which certificate authority to choose. Your decision may be based on your past experiences, on the experiences of your friends or colleagues, or purely on monetary factors.
</para>
<para>
@@ -3146,11 +2894,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s2-secureserver-generatingkey">
<title>Generating a Key</title>
- <indexterm>
- <primary>secure server</primary>
- <secondary>key</secondary>
- <tertiary>generating</tertiary>
- </indexterm>
<para>
You must be root to generate a key.
</para>
@@ -3354,10 +3097,6 @@ ErrorDocument 404 /404-not_found.html</screen>
</section>
<section id="s1-use-new-key">
<title>How to configure the server to use the new key</title>
- <indexterm>
- <primary>Apache HTTP Server Keys</primary>
- <secondary>use new keys</secondary>
- </indexterm>
<para>
The steps to configure the Apache HTTP Server to use the new key are:
</para>
More information about the docs-commits
mailing list