From: Rich Bowen Date: Thu, 11 Jun 2026 20:15:48 +0000 (+0000) Subject: Rebuilds HTML, meta files X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5771f3abf7ce691e7f689c99c19bbe7437d31590;p=thirdparty%2Fapache%2Fhttpd.git Rebuilds HTML, meta files git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1935204 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index bdf5d2b2a8..5526bc0113 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -34,15 +34,16 @@ -

This document covers compilation and installation of the Apache HTTP Server - on Unix and Unix-like systems only. For compiling and - installation on Windows, see Using Apache HTTP Server with Microsoft - Windows and Compiling Apache for Microsoft Windows. - For other platforms, see the platform documentation.

+

The Apache HTTP Server is released as source code. This document + covers building and installing the server from source on Unix and + Unix-like systems. For Windows, see Using Apache HTTP Server with Microsoft + Windows and Compiling Apache httpd for Microsoft + Windows. For other platforms, see the platform documentation.

-

Apache httpd uses libtool and autoconf - to create a build environment that looks like many other Open Source - projects.

+

If you install httpd from a distribution package (RPM, DEB, etc.), + configuration layout and defaults may differ from what is described here. + See third-party packages below, and consult your + distribution's documentation for platform-specific details.

If you are upgrading from one minor version to the next (for example, 2.4.66 to 2.4.67), please skip down to the upgrading section.

@@ -66,45 +67,6 @@

Overview for the impatient

-
-
Installing on Fedora/CentOS/Red Hat Enterprise Linux
-
- 
sudo dnf install httpd
-
-# Start service
-sudo systemctl start httpd
-
-# Stop service
-sudo systemctl stop httpd
-
-# Restart service
-sudo systemctl restart httpd
- - -
See the - Fedora project's documentation for platform-specific notes.
-
- -
Installing on Ubuntu/Debian
-
-
sudo apt install apache2
-
-# Start service
-sudo systemctl start apache2
-
-# Stop service
-sudo systemctl stop apache2
-
-# Restart service
-sudo systemctl restart apache2
- - -
See Ubuntu's documentation for platform-specific notes.
- -
- -
Installing from source
-
@@ -164,12 +126,6 @@ $ cd httpd-NN

Each section of the compilation and installation process is described in more detail below, beginning with the requirements for compiling and installing Apache httpd.

- - - -
Don't see your favorite platform mentioned - here? Come help us - improve this doc.
top
@@ -187,19 +143,19 @@ $ cd httpd-NN (be sure the directory names do not have version numbers; for example, the APR distribution must be under /httpd_source_tree_root/srclib/apr/) and use ./configure's --with-included-apr - option. On some platforms, you may have to install the + option. On some platforms, you may have to install the corresponding -dev packages to allow httpd to build against your installed copy of APR and APR-Util. -
Perl-Compatible Regular Expressions Library (PCRE)
-
This library is required but no longer bundled with httpd. - Download the source code from https://www.pcre.org, - or install a Port or Package. If your build system can't find - the pcre-config script installed by the PCRE build, point to it - using the --with-pcre parameter. On some platforms, +
Perl-Compatible Regular Expressions Library (PCRE2)
+
This library is required but not bundled with httpd. + Download the source code from https://github.com/PCRE2Project/pcre2 + or install it from your system's package manager. If your build system can't find + the pcre2-config script installed by the PCRE2 build, + point to it using the --with-pcre parameter. On some platforms, you may have to install the corresponding -dev - package to allow httpd to build against your installed copy - of PCRE.
+ package (e.g. libpcre2-dev or pcre2-devel) + to allow httpd to build against your installed copy of PCRE2.
Disk Space
Make sure you have at least 200 MB of temporary free disk @@ -218,13 +174,11 @@ $ cd httpd-NN 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 investigate setting some time - synchronization facility on your system. Most modern Linux - distributions provide systemd-timesyncd or - chrony for this purpose. See the NTP - homepage for more details about NTP software and public - time servers.
+
HTTP protocol headers use timestamps, so your system clock + must be accurate. Most Linux distributions enable + systemd-timesyncd or chrony by + default. Verify that time synchronization is active on your + system before running a production server.
Perl 5 [OPTIONAL]
@@ -239,16 +193,13 @@ $ cd httpd-NN

Download

-

If you choose to build from source, start by downloading - the source tarball from the Apache HTTP Server - download site. The build process (described below) - allows you to customize your server to suit your - needs.

+

Download the source tarball from the Apache HTTP Server + download site.

After downloading, it is important to verify that you have a complete and unmodified 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 + PGP signature. Details on how to do this are available on the verification page.

@@ -269,11 +220,11 @@ $ cd httpd-NN

Configuring the source tree

-

The next step is to configure the Apache source tree for your +

The next step is to configure the httpd source tree for your particular platform and personal requirements. This is done using the script configure included in the root directory of the distribution. (Developers downloading - an unreleased version of the Apache source tree will need to have + an unreleased version of the httpd 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 official releases.)

@@ -284,14 +235,14 @@ $ cd httpd-NN and command line options.

The most important option is the location --prefix - where Apache is to be installed later, because Apache has to be - configured for this location to work correctly. More fine-tuned + where httpd is to be installed later, because httpd has to be + configured for this location to work correctly. More fine-tuned control of the location of files is possible with additional configure options.

Also at this point, you can specify which features you - want included in Apache by enabling and disabling modules. Apache comes with a wide range of modules - included by default. They will be compiled as + want included in httpd by enabling and disabling modules. httpd comes with a wide range of modules + included by default. They will be compiled as shared objects (DSOs) which can be loaded or unloaded at runtime. You can also choose to compile modules statically by using the option @@ -301,21 +252,21 @@ $ cd httpd-NN --enable-module option, where module is the name of the module with the mod_ string removed and with any underscore converted - to a dash. Similarly, you can disable modules with the - --disable-module option. Be careful when + to a dash. Similarly, you can disable modules with the + --disable-module option. Be careful when using these options, since configure cannot warn you if the module you specify does not exist; it will ignore the option.

In addition, it is sometimes necessary to provide the configure script with extra information about the - location of your compiler, libraries, or header files. This is + location of your compiler, libraries, or header files. This is done by passing either environment variables or command line - options to configure. For more information, see the + options to configure. For more information, see the configure manual page. Or invoke configure using the --help option.

For a short impression of what possibilities you have, here - is a typical example which compiles Apache for the installation + is a typical example which compiles httpd for the installation tree /sw/pkg/apache with a particular compiler and flags plus the two additional modules mod_ldap and mod_lua:

@@ -336,10 +287,11 @@ $ cd httpd-NN

Build

-

Now you can build the various parts which form the Apache +

Now you can build the various parts which form the httpd package by running:

-

$ make

+
$ make
+

Please be patient here, since a base configuration takes several minutes to compile and the time will vary widely @@ -353,7 +305,8 @@ $ cd httpd-NN installation PREFIX (see --prefix option above) by running:

-

$ make install

+
$ make install
+

This step will typically require root privileges, since PREFIX is usually a directory with restricted write @@ -365,23 +318,24 @@ $ cd httpd-NN

Customize

-

Next, you can customize your Apache HTTP server by editing +

Next, you can customize your Apache HTTP Server by editing the configuration files under PREFIX/conf/.

-

$ vi PREFIX/conf/httpd.conf

+
$ vi PREFIX/conf/httpd.conf
+
-

Have a look at the Apache manual under +

Have a look at the httpd manual under PREFIX/docs/manual/ or consult https://httpd.apache.org/docs/2.4/ for the most recent version of this manual and a complete reference of available configuration directives.

top

Test

-

Now you can start your Apache - HTTP server by immediately running:

+

Now you can start your Apache HTTP Server by immediately running:

-

$ PREFIX/bin/apachectl -k start

+
$ PREFIX/bin/apachectl -k start
+

You should then be able to request your first document via the URL http://localhost/. The web page you see is located @@ -390,27 +344,28 @@ $ cd httpd-NN Then stop the server again by running:

-

$ PREFIX/bin/apachectl -k stop

+
$ PREFIX/bin/apachectl -k stop
+
top

Upgrading

The first step in upgrading is to read the release announcement and the file CHANGES in the source distribution to - find any changes that may affect your site. When changing between + find any changes that may affect your site. When changing between major releases (for example, from 2.4 to 2.6), there will likely be major differences in the compile-time and - run-time configuration that will require manual adjustments. All + run-time configuration that will require manual adjustments. All modules will also need to be upgraded to accommodate changes in the module API.

Upgrading from one minor version to the next (for example, from - 2.4.66 to 2.4.67) is easier. The make install + 2.4.66 to 2.4.67) is easier. The make install process will not overwrite any of your existing documents, log - files, or configuration files. In addition, the developers make + files, or configuration files. In addition, the developers make every effort to avoid incompatible changes in the configure options, run-time configuration, or the - module API between minor versions. In most cases you should be able to + module API between minor versions. In most cases you should be able to use an identical configure command line, an identical configuration file, and all of your modules should continue to work.

@@ -418,9 +373,9 @@ $ cd httpd-NN

To upgrade across minor versions, start by finding the file config.nice in the build directory of your installed server or at the root of the source tree for your - old install. This will contain the exact + old install. This will contain the exact configure command line that you used to - configure the source tree. Then to upgrade from one version to + configure the source tree. Then to upgrade from one version to the next, you need only copy the config.nice file to the source tree of the new version, edit it to make any desired changes, and then run:

@@ -433,7 +388,7 @@ $ PREFIX/bin/apachectl -k start
You should always test any new version in your - environment before putting it into production. For example, you + environment before putting it into production. For example, you can install and run the new version along side the old one by using a different --prefix and a different port (by adjusting the Listen directive) to test for any @@ -443,32 +398,54 @@ $ PREFIX/bin/apachectl -k start which will be appended to your original configure options:

-

- $ ./config.nice --prefix=/home/test/apache --with-port=90 -

+ 
$ ./config.nice --prefix=/home/test/apache --with-port=90
+
top

Third-party packages

-

A large number of third parties provide their own packaged - distributions of the Apache HTTP Server for installation on - particular platforms. This includes the various Linux distributions, - various - Windows - packages, macOS, and many more.

+

Many operating systems ship pre-built Apache httpd packages. + These are convenient for getting started quickly, but they often + differ from a source build in configuration file layout, + compiled-in modules, and default paths. The documentation on this + site describes the server as built from source; if you are using a + platform package, consult your distribution's documentation for + platform-specific details.

+ +

Some common examples:

+ +
+
Fedora / CentOS / Red Hat Enterprise Linux
+
+ 
sudo dnf install httpd
+sudo systemctl start httpd
+ +

See the + Fedora project's documentation for configuration layout and + platform-specific notes.

+
+ +
Ubuntu / Debian
+
+
sudo apt install apache2
+sudo systemctl start apache2
+ +

See Ubuntu's + documentation for configuration layout and + platform-specific notes.

+
+

Our software license not only permits, but encourages, this kind of redistribution. However, it does result in a situation where the configuration layout and defaults on your installation of the server - may differ from what is stated in the documentation. While - unfortunate, this situation is not likely to change any time - soon.

- -

A description - of these third-party distributions is in the HTTP - Server wiki. However, you will need to familiarize - yourself with your particular platform's package management and - installation procedures.

+ may differ from what is stated in the documentation. A description + of these third-party distributions is available in the HTTP + Server wiki.

+ +
Don't see your favorite platform mentioned + here? Come help us + improve this doc.
diff --git a/docs/manual/install.html.fr.utf8 b/docs/manual/install.html.fr.utf8 index ab5488a582..8c27a80bf0 100644 --- a/docs/manual/install.html.fr.utf8 +++ b/docs/manual/install.html.fr.utf8 @@ -32,6 +32,8 @@  pt-br  |  tr 

+
Cette traduction peut être périmée. Vérifiez la version + anglaise pour les changements récents.

Ce document couvre l'installation et la compilation du serveur diff --git a/docs/manual/install.xml.de b/docs/manual/install.xml.de index eecab558f3..5d59d011a3 100644 --- a/docs/manual/install.xml.de +++ b/docs/manual/install.xml.de @@ -1,7 +1,7 @@ - + + diff --git a/docs/manual/install.xml.fr b/docs/manual/install.xml.fr index 3d5d9c46e6..32935144bb 100644 --- a/docs/manual/install.xml.fr +++ b/docs/manual/install.xml.fr @@ -3,7 +3,7 @@ - + + + + + + diff --git a/docs/manual/platform/win_compiling.html.en b/docs/manual/platform/win_compiling.html.en index 0f090e4bdf..56d01b3608 100644 --- a/docs/manual/platform/win_compiling.html.en +++ b/docs/manual/platform/win_compiling.html.en @@ -6,7 +6,7 @@ This file is generated from xml source: DO NOT EDIT XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --> -Compiling Apache for Microsoft Windows - Apache HTTP Server Version 2.4 +Compiling Apache httpd for Microsoft Windows - Apache HTTP Server Version 2.4 @@ -20,7 +20,7 @@

<-

Compiling Apache for Microsoft Windows

+Apache > HTTP Server > Documentation > Version 2.4 > Platform Specific Notes

Compiling Apache httpd for Microsoft Windows

Available Languages:  en  | diff --git a/docs/manual/platform/win_compiling.html.fr.utf8 b/docs/manual/platform/win_compiling.html.fr.utf8 index 3651569dbf..98f169cdbb 100644 --- a/docs/manual/platform/win_compiling.html.fr.utf8 +++ b/docs/manual/platform/win_compiling.html.fr.utf8 @@ -28,6 +28,8 @@  fr  |  ko 

+
Cette traduction peut être périmée. Vérifiez la version + anglaise pour les changements récents.

Il y a de nombreux points importants à connaître avant de diff --git a/docs/manual/platform/win_compiling.xml.fr b/docs/manual/platform/win_compiling.xml.fr index 2d5daf0cd0..20220d1385 100644 --- a/docs/manual/platform/win_compiling.xml.fr +++ b/docs/manual/platform/win_compiling.xml.fr @@ -1,7 +1,7 @@ - + diff --git a/docs/manual/platform/win_compiling.xml.ko b/docs/manual/platform/win_compiling.xml.ko index f8638a1909..9ce13060ce 100644 --- a/docs/manual/platform/win_compiling.xml.ko +++ b/docs/manual/platform/win_compiling.xml.ko @@ -1,7 +1,7 @@ - + - + + + +