Apache HTTP Server 2.0 官方文档

下载需积分: 9 | PDF格式 | 3.3MB | 更新于2025-01-05 | 2 浏览量 | 举报

"Apache HTTP Server 文档" Apache HTTP Server 文档是针对这个开源Web服务器的详尽参考资料，由Apache Software Foundation维护。这份文档是版本2.0的，发布于2005年10月6日，它包含了关于如何安装、配置、管理和优化Apache服务器的所有必要信息。文档的版权归Apache Software Foundation所有，并遵循Apache License 2.0的条款。Apache HTTP Server的文档是通过使用XSLT（Extensible Stylesheet Language Transformations）从XML源文件转换成LaTeX格式，再利用Apache Ant、Apache XML Xalan和Apache XML Xerces等工具进行处理。虽然HTML版的文档在开发过程中更为常见，但PDF版可能会存在一些错误或格式不一致的问题。如果遇到阅读困难，建议查阅Apache HTTP Server官网上的HTML版本。该文档的结构通常包括多个部分，如发布注记、升级指南、配置指令、模块详解、URL重写规则、安全性和性能调优等内容。例如，"Release Notes"章节提供了从1.3版本升级到2.0版本的指导，详细列出了新功能、改进和可能的兼容性问题。这有助于管理员了解如何平稳地迁移现有服务器设置。 "Upgrading to 2.0 from 1.3"章节至关重要，因为它涵盖了重要的更改，如配置文件的差异、API更新以及可能影响旧脚本和应用程序的接口修改。这部分内容会指导管理员如何处理升级过程中可能出现的问题，确保服务的连续性和稳定性。 Apache HTTP Server文档还包含各种模块的描述，这些模块扩展了服务器的功能，例如支持SSL/TLS加密、身份验证、缓存和日志记录。每个模块都有详细的配置选项和使用示例，帮助用户根据需求定制服务器行为。此外，文档还涵盖了服务器的管理和故障排除，提供了诊断和解决常见问题的方法。对于性能敏感的应用，文档会介绍如何调整服务器设置以提高响应速度和并发处理能力。 Apache HTTP Server的文档项目是由Apache HTTP Server Documentation Project维护的，有兴趣深入学习或者参与贡献的人可以在其官网找到更多信息和支持。 Apache HTTP Server文档是管理员和开发者不可或缺的资源，无论你是初学者还是经验丰富的专业人士，都可以从中获取全面、准确的指引来管理和优化你的Web服务器。

8 CHAPTER 1. RELEASE NOTES

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof,

You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability

obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only

on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You

agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted

against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the ﬁelds enclosed by brackets

"[]" replaced with your own identifying information. (Don’t include the brackets!) The text should be enclosed in

the appropriate comment syntax for the ﬁle format. We also recommend that a ﬁle or class name and description of

purpose be included on the same "printed page" as the copyright notice for easier identiﬁcation within third-party

archives.

Licensed under the Apache License, Version 2.0 (the "License");

you may not use this file except in compliance with the License.

You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

10 CHAPTER 2. USING THE APACHE HTTP SERVER

2.1 Compiling and Installing

This document covers compilation and installation of Apache on Unix and Unix-like systems only. For compiling and

installation on Windows, see Using Apache with Microsoft Windows (p. 209) . For other platforms, see the platform

(p. 208) documentation.

Apache 2.0’s conﬁguration and installation environment has changed completely from Apache 1.3. Apache 1.3 used

a custom set of scripts to achieve easy installation. Apache 2.0 now uses libtool and autoconf to create an

environment that looks like many other Open Source projects.

If you are upgrading from one minor version to the next (for example, 2.0.50 to 2.0.51), please skip down to the

upgrading section.

See also

• Conﬁgure the source tree (p. 245)

• Starting Apache (p. 14)

• Stopping and Restarting (p. 16)

Overview for the impatient

Download $ lynx http://httpd.apache.org/download.cgi

Extract $ gzip -d httpd-2 0 NN.tar.gz

$ tar xvf httpd-2 0 NN.tar

Conﬁgure $ ./configure --prefix=PREFIX

Compile $ make

Install $ make install

Customize $ vi PREFIX/conf/httpd.conf

Test $ PREFIX/bin/apachectl start

NN must be replaced with the current minor version number, and PREFIX must be replaced with the ﬁlesystem path

under which the server should be installed. If PREFIX is not speciﬁed, it defaults to /usr/local/apache2.

Each section of the compilation and installation process is described in more detail below, beginning with the require-

ments for compiling and installing Apache HTTPD.

Requirements

The following requirements exist for building Apache:

Disk Space Make sure you have at least 50 MB of temporary free disk space available. After installation Apache

occupies approximately 10 MB of disk space. The actual disk space requirements will vary considerably based

on your chosen conﬁguration options and any third-party modules.

ANSI-C Compiler and Build System Make sure you have an ANSI-C compiler installed. The GNU C compiler

(GCC)

from the Free Software Foundation (FSF)

is recommended (version 2.7.2 is ﬁne). If you don’t have

GCC then at least make sure your vendor’s compiler is ANSI compliant. In addition, your PATH must contain

basic build tools such as make.

Accurate time keeping Elements of the HTTP protocol are expressed as the time of day. So, it’s time to investi-

gate setting some time synchronization facility on your system. Usually the ntpdate or xntpd programs

http://www.gnu.org/software/gcc/gcc.html

http://www.gnu.org/

2.1. COMPILING AND INSTALLING 11

are used for this purpose which are based on the Network Time Protocol (NTP). See the Usenet newsgroup

comp.protocols.time.ntp

and the NTP homepage

for more details about NTP software and public time servers.

Perl 5

[OPTIONAL] For some of the support scripts like apxs or dbmmanage (which are written in Perl) the Perl 5

interpreter is required (versions 5.003 or newer are sufﬁcient). If you have multiple Perl interpreters (for exam-

ple, a systemwide install of Perl 4, and your own install of Perl 5), you are advised to use the --with-perl

option (see below) to make sure the correct one is used by conﬁgure. If no Perl 5 interpreter is found by the

conﬁgure script, you will not be able to use the affected support scripts. Of course, you will still be able to build

and use Apache 2.0.

Download

Apache can be downloaded from the Apache HTTP Server download site

which lists several mirrors. Most users

of Apache on unix-like systems will be better off downloading and compiling a source version. The build process

(described below) is easy, and it allows you to customize your server to suit your needs. In addition, binary releases

are often not up to date with the latest source releases. If you do download a binary, follow the instructions in the

INSTALL.bindist ﬁle inside the distribution.

After downloading, it is important to verify that you have a complete and unmodiﬁed version of the Apache HTTP

Server. This can be accomplished by testing the downloaded tarball against the PGP signature. Details on how to do

this are available on the download page

and an extended example is available describing the use of PGP

Extract

Extracting the source from the Apache HTTPD tarball is a simple matter of uncompressing, and then untarring:

$ gzip -d httpd-2 0 NN.tar.gz

$ tar xvf httpd-2 0 NN.tar

This will create a new directory under the current directory containing the source code for the distribution. You should

cd into that directory before proceeding with compiling the server.

Conﬁguring the source tree

The next step is to conﬁgure the Apache source tree for your particular platform and personal requirements. This

is done using the script conﬁgure included in the root directory of the distribution. (Developers downloading the

CVS version of the Apache source tree will need to have autoconf and libtool installed and will need to run

buildconf before proceeding with the next steps. This is not necessary for ofﬁcial releases.)

To conﬁgure the source tree using all the default options, simply type ./configure. To change the default options,

conﬁgure accepts a variety of variables and command line options.

The most important option is the location --prefix where Apache is to be installed later, because Apache has to

be conﬁgured for this location to work correctly. More ﬁne-tuned control of the location of ﬁles is possible with

additional conﬁgure options (p. 245) .

Also at this point, you can specify which features (p. 245) you want included in Apache by enabling and disabling

modules (p. 654) . Apache comes with a Base (p. 296) set of modules included by default. Other modules are enabled

news:comp.protocols.time.ntp

http://www.ntp.org

http://httpd.apache.org/download.cgi

http://httpd.apache.org/download.cgi#verify

http://httpd.apache.org/dev/veriﬁcation.html

12 CHAPTER 2. USING THE APACHE HTTP SERVER

using the --enable-module option, where module is the name of the module with the mod string removed and

with any underscore converted to a dash. You can also choose to compile modules as shared objects (DSOs) (p. 44) –

which can be loaded or unloaded at runtime – by using the option --enable-module=shared. Similarly, you can

disable Base modules with the --disable-module option. Be careful when using these options, since conﬁgure

cannot warn you if the module you specify does not exist; it will simply ignore the option.

In addition, it is sometimes necessary to provide the conﬁgure script with extra information about the location of your

compiler, libraries, or header ﬁles. This is done by passing either environment variables or command line options to

conﬁgure. For more information, see the conﬁgure manual page.

For a short impression of what possibilities you have, here is a typical example which compiles Apache for the instal-

lation tree /sw/pkg/apache with a particular compiler and ﬂags plus the two additional modules MOD REWRITE

and MOD SPELING for later loading through the DSO mechanism:

$ CC="pgcc" CFLAGS="-O2" \

./configure --prefix=/sw/pkg/apache \

--enable-rewrite=shared \

--enable-speling=shared

When conﬁgure is run it will take several minutes to test for the availability of features on your system and build

Makeﬁles which will later be used to compile the server.

Details on all the different conﬁgure options are available on the conﬁgure manual page.

Build

Now you can build the various parts which form the Apache package by simply running the command:

$ make

Please be patient here, since a base conﬁguration takes approximately 3 minutes to compile under a Pentium III/Linux

2.2 system, but this will vary widely depending on your hardware and the number of modules which you have enabled.

Install

Now it’s time to install the package under the conﬁgured installation PREFIX (see --prefix option above) by

running:

$ make install

If you are upgrading, the installation will not overwrite your conﬁguration ﬁles or documents.

Customize

Next, you can customize your Apache HTTP server by editing the conﬁguration ﬁles (p. 19) under PREFIX/conf/.

$ vi PREFIX/conf/httpd.conf

Have a look at the Apache manual under docs/manual/ (p. ??) or consult http://httpd.apache.org/docs-2.0/ for the most

recent version of this manual and a complete reference of available conﬁguration directives (p. 657) .

剩余684页未读，继续阅读

liangyuliang0335

粉丝: 0
资源: 1

Apache HTTP Server 2.0 官方文档

Java使用Apache POI处理Word doc文件

PHPDoc扩展提升Apache Cassandra驱动文档自动完成体验

掌握Apache CHM详解，全面理解Apache 2配置

apache doc - chm

apache doc 中文文档-html

APACHE.doc

LoadRunner监控Apache.doc

apache2.2_doc

apache配置.doc

apache httpclient 4.5.1 doc

最新资源