With a share of more than 50%, the Apache HTTP Server (Apache) is the world's most widely-used Web server according to the Survey from http://www.netcraft.com/. Apache, developed by the Apache Software Foundation (http://www.apache.org/), is available for most operating systems. SUSE® Linux Enterprise Server includes Apache version 2.2. In this chapter, learn how to install, configure and set up a Web server; how to use SSL, CGI, and additional modules; and how to troubleshoot Apache.
With the help of this section, quickly set up and start Apache. You must
root to install and configure Apache.
Make sure the following requirements are met before trying to set up the Apache Web server:
The machine's network is configured properly. For more information about this topic, refer to Chapter 20, Basic Networking.
The machine's exact system time is maintained by synchronizing with a time server. This is necessary because parts of the HTTP protocol depend on the correct time. See Chapter 22, Time Synchronization with NTP to learn more about this topic.
The latest security updates are installed. If in doubt, run a YaST Online Update.
The default Web server port (
80) is opened in the
firewall. For this, configure the SuSEFirewall2 to allow the service
in the external zone. This can be done
using YaST. See Section “Configuring the Firewall with YaST” (Chapter 15, Masquerading and Firewalls, ↑Security Guide) for
Apache on SUSE Linux Enterprise Server is not installed by default. To install it with a standard, predefined configuration that runs “out of the box”, proceed as follows:
Procedure 29.1. Installing Apache with the Default Configuration
Start YaST and select+ .
Choose+ and select int .
Confirm the installation of the dependent packages to finish the installation process.
The installation includes the multiprocessing module
apache2-prefork as well as the PHP5 module.
Refer to Section 29.4, “Installing, Activating, and Configuring Modules” for more information
You can start Apache automatically at boot time or start it manually.
Procedure 29.2. Starting Apache Automatically
To make sure that Apache is automatically started during boot in
5, execute the
chkconfig -a apache2
Alternatively, start YaST and select+ .
Search for apache2 and the service.
The Web server starts immediately.
Save your changes with.
The system is configured to automatically start Apache in runlevels
5 during boot.
For more information about the runlevels in SUSE Linux Enterprise Server and a description of the YaST runlevel editor, refer to Section 9.2.3, “Configuring System Services (Runlevel) with YaST”.
To manually start Apache using the shell, run rcapache2 start.
Procedure 29.3. Checking if Apache is Running
If you do not receive error messages when starting Apache, this usually indicates that the Web server is running. To test this:
Now that the Web server is running, you can add your own documents, adjust the configuration according to your needs, or add functionality by installing modules.
SUSE Linux Enterprise Server offers two configuration options:
Manual configuration offers a higher level of detail, but lacks the convenience of the YaST GUI.
|Reload or Restart Apache after Configuration Changes|
Most configuration changes require a reload (some also a restart) of
Apache to take effect. Manually reload Apache with
If you configure Apache with YaST, this can be taken care of automatically if you set Section 18.104.22.168, “HTTP Server Configuration”.to as described in
This section gives an overview of the Apache configuration files. If you use YaST for configuration, you do not need to touch these files—however, the information might be useful for you if you want to switch to manual configuration later on.
Apache configuration files can be found in two different locations:
/etc/sysconfig/apache2 controls some global
settings of Apache, like modules to load, additional configuration
files to include, flags with which the server should be started, and
flags that should be added to the command line. Every configuration
option in this file is extensively documented and therefore not
mentioned here. For a general-purpose Web server, the settings in
/etc/sysconfig/apache2 should be sufficient for
any configuration needs.
/etc/apache2/ hosts all configuration files for
Apache. In the following, the purpose of each file is explained. Each
file includes several configuration options (also referred to as
directives). Every configuration option in these
files is extensively documented and therefore not mentioned here.
The Apache configuration files are organized as follows:
/etc/apache2/ | |- charset.conv |- conf.d/ | | | |- *.conf | |- default-server.conf |- errors.conf |- httpd.conf |- listen.conf |- magic |- mime.types |- mod_*.conf |- server-tuning.conf |- ssl.* |- ssl-global.conf |- sysconfig.d | | | |- global.conf | |- include.conf | |- loadmodule.conf . . | |- uid.conf |- vhosts.d | |- *.conf
Apache Configuration Files in /etc/apache2/
Specifies which character sets to use for different languages. Do not edit this file.
Configuration files added by other modules. These configuration
files can be included into your virtual host configuration where
examples. By doing so, you can provide different module sets for
different virtual hosts.
Global configuration for all virtual hosts with reasonable defaults. Instead of changing the values, overwrite them with a virtual host configuration.
Defines how Apache responds to errors. To customize these messages for all virtual hosts, edit this file. Otherwise overwrite these directives in your virtual host configurations.
The main Apache server configuration file. Avoid changing this file. It primarily contains include statements and global settings. Overwrite global settings in the pertinent configuration files listed here. Change host-specific settings (such as document root) in your virtual host configuration.
Binds Apache to specific IP addresses and ports. Name-based virtual hosting is also configured here. For details, see Section 22.214.171.124.1, “Name-Based Virtual Hosts”.
Data for the mime_magic module that helps Apache automatically determine the MIME type of an unknown file. Do not change this file.
MIME types known by the system (this actually is a link to
/etc/mime.types). Do not edit this file. If you
need to add MIME types not listed here, add them to
Configuration files for the modules that are installed by default.
Refer to Section 29.4, “Installing, Activating, and Configuring Modules” for details.
Note that configuration files for optional modules reside in the
Contains configuration directives for the different MPMs (see Section 29.4.4, “Multiprocessing Modules”) as well as general configuration options that control Apache's performance. Properly test your Web server when making changes here.
Global SSL configuration and SSL certificate data. Refer to Section 29.6, “Setting Up a Secure Web Server with SSL” for details.
Configuration files automatically generated from
/etc/sysconfig/apache2. Do not change any of
instead. Do not put other configuration files in this directory.
Specifies under which user and group ID Apache runs. Do not change this file.
Your virtual host configuration should be located here. The
directory contains template files for virtual hosts with and without
SSL. Every file in this directory ending with
.conf is automatically included in the Apache
configuration. Refer to
Section 126.96.36.199, “Virtual Host Configuration” for
Configuring Apache manually involves editing plain text configuration
files as user
The term virtual host refers to Apache's ability to serve multiple universal resource identifiers (URIs) from the same physical machine. This means that several domains, such as www.example.com and www.example.net, are run by a single Web server on one physical machine.
It is common practice to use virtual hosts to save administrative effort (only a single Web server needs to be maintained) and hardware expenses (each domain does not require a dedicated server). Virtual hosts can be name based, IP based, or port based.
To list all existing virtual hosts, use the command httpd2
-S. This outputs a list showing the default
server and all virtual hosts together with their IP addresses and
listening ports. Furthermore, the list also contains an entry for each
virtual host showing its location in the configuration files.
Virtual hosts can be configured via YaST as described in
Section 188.8.131.52.4, “Virtual Hosts”
or by manually editing a configuration file. By default, Apache in
SUSE Linux Enterprise Server is prepared for one configuration file per virtual host
/etc/apache2/vhosts.d/. All files in this
directory with the extension
automatically included to the configuration. A basic template for a
virtual host is provided in this directory
vhost-ssl.template for a virtual host with SSL
|Always Create a Virtual Host Configuration|
It is recommended to always create a virtual host configuration file, even if your Web server only hosts one domain. By doing so, you not only have the domain-specific configuration in one file, but you can always fall back to a working basic configuration by simply moving, deleting, or renaming the configuration file for the virtual host. For the same reason, you should also create separate configuration files for each virtual host.
When using name-based virtual hosts it is recommended to set up a
default configuration that will be used when a domain name does not
match a virtual host configuration. The default virtual host is the
one whose configuration is loaded first. Since the order of the
configuration files is determined by filename, start the filename of
the default virtual host configuration with an underscore character
block holds the information that applies to a particular domain. When
Apache receives a client request for a defined virtual host, it uses
the directives enclosed in this section. Almost all directives can be
used in a virtual host context. See
for further information about Apache's configuration directives.
With name-based virtual hosts, more than one Web site is served per IP
address. Apache uses the host field in the HTTP header that is sent by
the client to connect the request to a matching
ServerName entry of one of the virtual host
declarations. If no matching
found, the first specified virtual host is used as a default.
NameVirtualHost tells Apache on
which IP address and, optionally, which port it should listen to for
requests by clients containing the domain name in the HTTP header.
This option is configured in the configuration file
The first argument can be a fully qualified domain name, but it is
recommended to use the IP address. The second argument is the port and
is optional. By default, port
80 is used and
is configured via the
The wild card
* can be used for both the IP address
and the port number to receive requests on all interfaces. IPv6
addresses must be enclosed in square brackets.
Example 29.1. Variations of Name-Based
[:Port]NameVirtualHost 192.168.3.100:80 NameVirtualHost 192.168.3.100 NameVirtualHost *:80 NameVirtualHost * NameVirtualHost [2002:c0a8:364::]:80
VirtualHost tag takes the IP
address (or fully qualified domain name) previously declared with the
NameVirtualHost as an argument in a
name-based virtual host configuration. A port number previously
declared with the
The wild card * is also allowed as a substitute
for the IP address. This syntax is only valid in combination with the
wild card usage in
NameVirtualHost * . When
using IPv6 addresses, the address must be included in square brackets.
Example 29.2. Name-Based
<VirtualHost 192.168.3.100:80> ... </VirtualHost> <VirtualHost 192.168.3.100> ... </VirtualHost> <VirtualHost *:80> ... </VirtualHost> <VirtualHost *> ... </VirtualHost> <VirtualHost [2002:c0a8:364::]> ... </VirtualHost>
This alternative virtual host configuration requires the setup of multiple IPs for a machine. One instance of Apache hosts several domains, each of which is assigned a different IP.
The physical server must have one IP address for each IP-based virtual host. If the machine does not have multiple network cards, virtual network interfaces (IP aliasing) can also be used.
The following example shows Apache running on a machine with the IP
192.168.3.100, hosting two
domains on the additional IPs
192.168.3.102. A separate
VirtualHost block is needed for every virtual
Example 29.3. IP-Based
<VirtualHost 192.168.3.101> ... </VirtualHost> <VirtualHost 192.168.3.102> ... </VirtualHost>
VirtualHost directives are only
specified for interfaces other than
Listen directive is also configured
192.168.3.100, a separate IP-based virtual host
must be created to answer HTTP requests to that
interface—otherwise the directives found in the default server
At least the following directives should be present in each virtual
host configuration in order to set up a virtual host. See
/etc/apache2/vhosts.d/vhost.template for more
The fully qualified domain name under which the host should be addressed.
Path to the directory from which Apache should serve files for this
host. For security reasons, access to the entire file system is
forbidden by default, so you must explicitly unlock this directory
E-mail address of the server administrator. This address is, for example, shown on error pages Apache creates.
The error log file for this virtual host. Although it is not
necessary to create separate error log files for each virtual host,
it is common practice to do so, because it makes the debugging of
errors much easier.
/var/log/apache2/ is the
default directory for Apache's log files.
The access log file for this virtual host. Although it is not
necessary to create separate access log files for each virtual
host, it is common practice to do so, because it allows the
separate analysis of access statistics for each host.
/var/log/apache2/ is the default directory for
Apache's log files.
As mentioned above, access to the whole file system is forbidden by
default for security reasons. Therefore, explicitly unlock the
directories in which you have placed the files Apache should
serve—for example the
<Directory "/srv/www/www.example.com/htdocs"> Order allow,deny Allow from all </Directory>
The complete configuration file looks like this:
Example 29.4. Basic
<VirtualHost 192.168.3.100> ServerName www.example.com DocumentRoot /srv/www/www.example.com/htdocs ServerAdmin firstname.lastname@example.org ErrorLog /var/log/apache2/www.example.com_log CustomLog /var/log/apache2/www.example.com-access_log common <Directory "/srv/www/www.example.com/htdocs"> Order allow,deny Allow from all </Directory> </VirtualHost>
To configure your Web server with YaST, start YaST and select Section 184.108.40.206, “HTTP Server Configuration”.+ . When starting the module for the first time, the starts, prompting you to make a few basic decisions concerning administration of the server. After having finished the wizard, the dialog starts each time you call the module. For more information, see
The HTTP Server Wizard consists of five steps. In the last step of the dialog, you are given the opportunity to enter the expert configuration mode to make even more specific settings.
Here, specify the network interfaces and ports Apache uses to listen for
incoming requests. You can select any combination of existing network
interfaces and their respective IP addresses. Ports from all three
ranges (well-known ports, registered ports, and dynamic or private
ports) that are not reserved by other services can be used. The default
setting is to listen on all network interfaces (IP addresses) on port
Checkto open the ports in the firewall that the Web server listens on. This is necessary to make the Web server available on the network, which can be a LAN, WAN, or the public Internet. Keeping the port closed is only useful in test situations where no external access to the Web server is necessary. If you have multiple network interfaces, click to specify on which interface(s) the port(s) should be opened.
Clickto continue with the configuration.
The Section 220.127.116.11.2, “Server Modules”. Click to advance to the next dialog.configuration option allows for the activation or deactivation of the script languages that the Web server should support. For the activation or deactivation of other modules, refer to
This option pertains to the default Web server. As explained in Section 18.104.22.168, “Virtual Host Configuration”, Apache can serve multiple virtual hosts from a single physical machine. The first declared virtual host in the configuration file is commonly referred to as the default host. Each virtual host inherits the default host's configuration.
To edit the host settings (also called directives), choose the appropriate entry in the table then click . To add new directives, click . To delete a directive, select it and click .
Here is list of the default settings of the server:
Path to the directory from which Apache serves files for this host.
/srv/www/htdocs is the default location.
With the help of
Alias directives, URLs can
be mapped to physical file system locations. This means that a
certain path even outside the
Document Root in the
file system can be accessed via a URL aliasing that path.
The default SUSE Linux Enterprise Server
/icons points to
/usr/share/apache2/icons for the Apache icons
displayed in the directory index view.
Similar to the
Alias directive, the
ScriptAlias directive maps a URL to a file
system location. The difference is that
ScriptAlias designates the target directory
as a CGI location, meaning that CGI scripts should be executed in
Directory settings, you can enclose a
group of configuration options that will only apply to the specified
Access and display options for the directories
/srv/www/cgi-bin are configured here. It should
not be necessary to change the defaults.
With include, additional configuration files can be specified. Two
Include directives are already
/etc/apache2/conf.d/ is the
directory containing the configuration files that come with external
modules. With this directive, all files in this directory ending in
.conf are included. With the second directive,
apache2-manual configuration file is included.
This specifies the default URL used by clients to contact the Web
server. Use a fully qualified domain name (FQDN) to reach the Web
or its IP address. You cannot choose an arbitrary name here—the
server must be “known” under this name.
Server Administrator E-Mail
E-mail address of the server administrator. This address is, for example, shown on error pages Apache creates.
After finishing with thestep, click to continue with the configuration.
In this step, the wizard displays a list of already configured virtual hosts (see Section 22.214.171.124, “Virtual Host Configuration”). If you have not made manual changes prior to starting the YaST HTTP wizard, no virtual host is present.
To add a host, click
DocumentRoot), and the . is used to
determine how a host is identified (name based or IP based). Specify the
name or IP address with
Clickingadvances to the second part of the virtual host configuration dialog.
In part two of the virtual host configuration you can specify whether or
not to enable CGI scripts and which directory to use for these scripts.
It is also possible to enable SSL. If you do so, you must specify the
path to the certificate as well. See
Section 29.6.2, “Configuring Apache with SSL” for details on SSL and
certificates. With the option, you
can specify which file to display when the client requests a directory
index.html). Add one or more filenames
(space-separated) if you want to change this. With , the content of the users public directories
made available on the server under
|Creating Virtual Hosts|
It is not possible to add virtual hosts at will. If using name-based virtual hosts, each hostname must be resolved on the network. If using IP-based virtual hosts, you can assign only one host to each IP address available.
This is the final step of the wizard. Here, determine how and when the Apache server is started: when booting or manually. Also see a short summary of the configuration made so far. If you are satisfied with your settings, click Section 126.96.36.199, “HTTP Server Configuration”.to complete configuration. If you want to change something, click until you have reached the desired dialog. Clicking opens the dialog described in
Thedialog also lets you make even more adjustments to the configuration than the wizard (which only runs if you configure your Web server for the first time). It consists of four tabs described in the following. No configuration option you change here is effective immediately—you always must confirm your changes with to make them effective. Clicking leaves the configuration module and discards your changes.
80. You should always check , because otherwise the Web server is not reachable
from outside. Keeping the port closed is only useful in test situations
where no external access to the Web server is necessary. If you have
multiple network interfaces, click to specify on which interface(s) the port(s) should
With Section 29.3, “Starting and Stopping Apache”. These commands are effective immediately and their log messages are also displayed immediately., watch either the access log or the error log. This is useful if you want to test your configuration. The log file opens in a separate window from which you can also restart or reload the Web server. For details, see
You can change the status (enabled or disabled) of Apache2 modules by clicking Section 29.4, “Installing, Activating, and Configuring Modules”.. Click to add a new module that is already installed but not yet listed. Learn more about modules in
If configured with YaST as described in Section 29.2.3, “Configuring Apache with YaST”, Apache is started at boot time in runlevels 3 and 5 and stopped in runlevels 0, 1, 2, and 6. You can change this behavior using YaST's runlevel editor or the command line tool chkconfig.
To start, stop, or manipulate Apache on a running system, use the init script /usr/sbin/rcapache2. For general information about init scripts, refer to Section 9.2.2, “Init Scripts”. The rcapache2 command takes the following parameters:
Checks if Apache is started.
Starts Apache if it is not already running.
Starts Apache with SSL support if it is not already running. For more information about SSL support, refer to Section 29.6, “Setting Up a Secure Web Server with SSL”.
Stops Apache by terminating the parent process.
Stops and then restarts Apache. Starts the Web server if it was not running before.
Stops then restarts Apache only if it is already running.
Stops the Web server by advising all forked Apache processes to first finish their requests before shutting down. As each process dies, it is replaced by a newly started one, resulting in a complete “restart” of Apache.
|Restarting Apache in Production Environments|
To activate changes in the Apache configuration without causing
connection break-offs, use the
Starts a second Web server that immediately serves all incoming
requests. The previous instance of the Web server continues to handle
all existing requests for a defined period of time configured with
either useful when upgrading to a new version or when having changed
configuration options that require a restart. Using this option
ensures a minimum server downtime.
GracefulShutdownTimeout needs to be set,
restart-graceful will result in a regular
restart. If set to zero, the server will wait indefinitely until all
remaining requests have been fully served.
A graceful restart can fail if the original Apache instance is not able to clear all necessary resources. In this case, the command will result in a graceful stop.
Stops the Web server after a defined period of time configured with
GracefulShutdownTimeout in order to ensure
that existing requests can be finished.
GracefulShutdownTimeout needs to be set,
stop-graceful will result in a regular
restart. If set to zero, the server will wait indefinitely until all
remaining requests have been fully served.
Checks the syntax of the configuration files without affecting a
running Web server. Because this check is forced every time the server
is started, reloaded, or restarted, it is usually not necessary to run
the test explicitly (if a configuration error is found, the Web server
is not started, reloaded, or restarted). The
extreme-configtest options start the Web server as
nobody and actually
load the configuration, so more errors can be detected. Note that
although the configuration is loaded, it is not possible to test the
SSL setup because the SSL certificates cannot be read by
Probes for the necessity of a reload (checks whether the configuration has changed) and suggests the required arguments for the rcapache2 command.
server-status and full-server-status
Dumps a short or full status screen, respectively. Requires either
lynx or w3m installed as well as the module
mod_status enabled. In addition to that,
status must be added to
APACHE_SERVER_FLAGS in the file
If you specify additional flags to the rcapache2, these are passed through to the Web server.
The Apache software is built in a modular fashion: all functionality except some core tasks are handled by modules. This has progressed so far that even HTTP is processed by a module (http_core).
Apache modules can be compiled into the Apache binary at build time or dynamically loaded at runtime. Refer to Section 29.4.2, “Activation and Deactivation” for details of how to load modules dynamically.
Apache modules can be divided into four different categories:
Base modules are compiled into Apache by default. Apache in
SUSE Linux Enterprise Server has only
mod_so (needed to load
other modules) and
http_core compiled in. All
others are available as shared objects: rather than being included in
the server binary itself, they can be included at runtime.
In general, modules labeled as extensions are included in the Apache software package, but are usually not compiled into the server statically. In SUSE Linux Enterprise Server, they are available as shared objects that can be loaded into Apache at runtime.
Modules labeled external are not included in the official Apache distribution. However, SUSE Linux Enterprise Server provides several of them.
MPMs are responsible for accepting and handling requests to the Web server, representing the core of the Web server software.
If you have done a default installation as described in
Section 29.1.2, “Installation”, the following
modules are already installed: all base and extension modules, the
multiprocessing module Prefork MPM, and the external modules
You can install additional external modules by starting YaST and choosing apache. Among other packages, the results list contains all available external Apache modules.+ . Now choose + and search for
Activate or deactivate particular modules either manually or with YaST. In YaST, script language modules (PHP5, Perl, and Python) need to be enabled or disabled with the module configuration described in Section 188.8.131.52, “HTTP Server Wizard”. All other modules can be enabled or disabled as described in Section 184.108.40.206.2, “Server Modules”.
If you prefer to activate or deactivate the modules manually, use the
respectively. a2enmod -l outputs a list of all
currently active modules.
|Including Configuration Files for External Modules|
If you have activated external modules manually, make sure to load
their configuration files in all virtual host configurations.
Configuration files for external modules are located under
All base and extension modules are described in detail in the Apache documentation. Only a brief description of the most important modules is available here. Refer to http://httpd.apache.org/docs/2.2/mod/ to learn details about each module.
Provides methods to execute a script whenever a certain MIME type
application/pdf), a file with a
specific extension (like
.rpm), or a certain
request method (such as
GET) is requested.
This module is enabled by default.
Redirect directives with which you can map a
URl to a specific directory (
redirect a requested URL to another location. This module is enabled
The authentication modules provide different authentication methods:
basic authentication with
digest authentication with
Digest authentication in Apache 2.2 is considered experimental.
mod_auth_digest must be combined with an
authentication provider module,
mod_authn_file for text
file–based authentication) and with an authorization module
mod_authz_* (for example,
mod_authz_user for user authorization).
More information about this topic is available in the Authentication HOWTO at http://httpd.apache.org/docs/2.2/howto/auth.html.
Autoindex generates directory listings when no index file (for
index.html) is present. The look and
feel of these indexes is configurable. This module is enabled by
default. However, directory listings are disabled by default via the
Options directive—overwrite this
setting in your virtual host configuration. The default configuration
file for this module is located at
mod_cgi is needed to execute CGI scripts.
This module is enabled by default.
Using this module, Apache can be configured to compress given file types on the fly before delivering them.
mod_dir provides the
DirectoryIndex directive with which you can
configure which files are automatically delivered when a directory is
index.html by default). It also
provides an automatic redirect to the correct URL when a directory
request does not contain a trailing slash. This module is enabled by
Controls the environment that is passed to CGI scripts or SSI pages. Environment variables can be set or unset or passed from the shell that invoked the httpd process. This module is enabled by default.
mod_expires, you can control how often
proxy and browser caches refresh your documents by sending an
Expires header. This module is enabled by
mod_include lets you use Server Side
Includes (SSI), which provide a basic functionality to generate HTML
pages dynamically. This module is enabled by default.
Provides a comprehensive overview of the server configuration under
http://localhost/server-info/. For security reasons, you should
always limit access to this URL. By default only
localhost is allowed to
access this URL.
mod_info is configured at
With this module, you can configure the look of the Apache log files. This module is enabled by default.
The mime module makes certain that a file is delivered with the
correct MIME header based on the filename's extension (for example
text/html for HTML documents). This module
is enabled by default.
Necessary for content negotiation. See http://httpd.apache.org/docs/2.2/content-negotiation.html for more information. This module is enabled by default.
Provides the functionality of
offers more features and flexibility. With
mod_rewrite, you can redirect URLs based on
multiple rules, request headers, and more.
Sets environment variables based on details of the client's request, such as the browser string the client sends, or the client's IP address. This module is enabled by default.
mod_speling attempts to automatically
correct typographical errors in URLs, such as capitalization errors.
Enables encrypted connections between Web server and clients. See Section 29.6, “Setting Up a Secure Web Server with SSL” for details. This module is enabled by default.
Provides information on server activity and performance under
http://localhost/server-status/. For security reasons, you should
always limit access to this URL. By default, only
localhost is allowed to
access this URL.
mod_status is configured at
mod_suexec lets you run CGI scripts under a
different user and group. This module is enabled by default.
Enables user-specific directories available under
UserDir directive must be specified in the
configuration. This module is enabled by default.
SUSE Linux Enterprise Server provides two different multiprocessing modules (MPMs) for use with Apache:
The prefork MPM implements a nonthreaded, preforking Web server. It makes the Web server behave similarly to Apache version 1.x. In this version it isolates each request and handles it by forking a separate child process. Thus problematic requests cannot affect others, avoiding a lockup of the Web server.
While providing stability with this process-based approach, the prefork MPM consumes more system resources than its counterpart, the worker MPM. The prefork MPM is considered the default MPM for Unix-based operating systems.
|MPMs in This Document|
This document assumes Apache is used with the prefork MPM.
The worker MPM provides a multi-threaded Web server. A thread is a “lighter” form of a process. The advantage of a thread over a process is its lower resource consumption. Instead of only forking child processes, the worker MPM serves requests by using threads with server processes. The preforked child processes are multi-threaded. This approach makes Apache perform better by consuming fewer system resources than the prefork MPM.
One major disadvantage is the stability of the worker MPM: if a thread becomes corrupt, all threads of a process can be affected. In the worst case, this may result in a server crash. Especially when using the Common Gateway Interface (CGI) with Apache under heavy load, internal server errors might occur due to threads being unable to communicate with system resources. Another argument against using the worker MPM with Apache is that not all available Apache modules are thread-safe and thus cannot be used in conjunction with the worker MPM.
|Using PHP Modules with MPMs|
Not all available PHP modules are thread-safe. Using the worker MPM
Find a list of all external modules shipped with SUSE Linux Enterprise Server here. Find the module's documentation in the listed directory.
Adds support to Apache to provide Novell AppArmor confinement to individual CGI
scripts handled by modules like
Package Name: |
|More Information: Part “Confining Privileges with Novell AppArmor” (↑Security Guide)|
mod_mono allows you to run ASP.NET
pages in your server.
Package Name: |
mod_perl enables you to run Perl scripts in
an embedded interpreter. The persistent interpreter embedded in the
server avoids the overhead of starting an external interpreter and
the penalty of Perl start-up time.
Package Name: |
Configuration File: |
PHP is a server-side, cross-platform HTML embedded scripting language.
Package Name: |
Configuration File: |
mod_python allows embedding Python within
the Apache HTTP server for a considerable boost in performance and
added flexibility in designing Web-based applications.
Package Name: |
Apache can be extended by advanced users by writing custom modules. To
develop modules for Apache or compile third-party modules, the package
apache2-devel is required along with the
corresponding development tools.
also contains the apxs2 tools, which are necessary
for compiling additional modules for Apache.
apxs2 enables the compilation and installation of modules from source code (including the required changes to the configuration files), which creates dynamic shared objects (DSOs) that can be loaded into Apache at runtime.
The apxs2 binaries are located under
/usr/sbin/apxs2—suitable for building an
extension module that works with any MPM. The installation location is
prefork MPM modules. The installation location is
/usr/sbin/apxs2-worker—suitable for worker
MPM modules. The installation location is
Install and activate a module from source code with the following commands:
cd /path/to/module/source; apxs2 -cia
-c compiles the module,
installs it, and
-a activates it. Other options of
apxs2 are described in the
apxs2(1) man page.
Apache's Common Gateway Interface (CGI) lets you create dynamic content with programs or scripts usually referred to as CGI scripts. CGI scripts can be written in any programming language. Usually, script languages such as Perl or PHP are used.
To enable Apache to deliver content created by CGI scripts,
mod_cgi needs to be activated.
mod_alias is also needed. Both modules are
enabled by default. Refer to
Section 29.4.2, “Activation and Deactivation” for details on
Allowing the server to execute CGI scripts is a potential security hole. Refer to Section 29.7, “Avoiding Security Problems” for additional information.
In SUSE Linux Enterprise Server, the execution of CGI scripts is only allowed in the
/srv/www/cgi-bin/. This location is
already configured to execute CGI scripts. If you have created a virtual
host configuration (see
Section 220.127.116.11, “Virtual Host Configuration”) and
want to place your scripts in a host-specific directory, you must unlock
and configure this directory.
Example 29.5. VirtualHost CGI Configuration
ScriptAlias /cgi-bin/ "/srv/www/www.example.com/cgi-bin/" <Directory "/srv/www/www.example.com/cgi-bin/"> Options +ExecCGI AddHandler cgi-script .cgi .pl Order allow,deny Allow from all </Directory>
Tells Apache to handle all files within this directory as CGI scripts.
Enables CGI script execution
Tells the server to treat files with the extensions .pl and .cgi as CGI scripts. Adjust according to your needs.
CGI programming differs from "regular" programming in that the CGI
programs and scripts must be preceded by a MIME-Type header such as
Content-type: text/html. This header is sent to the
client, so it understands what kind of content it receives. Secondly,
the script's output must be something the client, usually a Web browser,
understands—HTML in most cases or plain text or images, for
A simple test script available under
/usr/share/doc/packages/apache2/test-cgi is part of
the Apache package. It outputs the content of some environment variables
as plain text. Copy this script to either
/srv/www/cgi-bin/ or the script directory of your
virtual host (
/srv/www/www.example.com/cgi-bin/) and name
Files accessible by the Web server should be owned by the user
root. For additional
information see Section 29.7, “Avoiding Security Problems”. Because the Web
server runs with a different user, the CGI scripts must be
world-executable and world-readable. Change into the CGI directory and
use the command chmod 755 test.cgi to apply the
http://www.example.com/cgi-bin/test.cgi. You should see the
“CGI/1.0 test script report”.
If you do not see the output of the test program but an error message instead, check the following:
Have you reloaded the server after having changed the configuration? Check with rcapache2 probe.
If you have configured your custom CGI directory, is it configured
properly? If in doubt, try the script within the default CGI directory
/srv/www/cgi-bin/ and call it with
Are the file permissions correct? Change into the CGI directory and execute ls -l test.cgi. Its output should start with
-rwxr-xr-x 1 root root
Make sure that the script does not contain programming errors. If you
have not changed
test.cgi, this should not be the
case, but if you are using your own programs, always make sure that
they do not contain programming errors.
Whenever sensitive data, such as credit card information, is transferred
between Web server and client, it is desirable to have a secure,
encrypted connection with authentication.
mod_ssl provides strong encryption using the
secure sockets layer (SSL) and transport layer security (TLS) protocols
for HTTP communication between a client and the Web server. Using
SSL/TSL, a private connection between Web server and client is
established. Data integrity is ensured and client and server are able to
authenticate each other.
For this purpose, the server sends an SSL certificate that holds information proving the server's valid identity before any request to a URL is answered. In turn, this guarantees that the server is the uniquely correct end point for the communication. Additionally, the certificate generates an encrypted connection between client and server that can transport information without the risk of exposing sensitive, plain-text content.
mod_ssl does not implement the SSL/TSL protocols
itself, but acts as an interface between Apache and an SSL library. In
SUSE Linux Enterprise Server, the OpenSSL library is used. OpenSSL is automatically
installed with Apache.
The most visible effect of using
Apache is that URLs are prefixed with
An example certificate for a hypothetical company “Snake
Oil” is available when installing the package
In order to use SSL/TSL with the Web server, you need to create an SSL certificate. This certificate is needed for the authorization between Web server and client, so that each party can clearly identify the other party. To ensure the integrity of the certificate, it must be signed by a party every user trusts.
There are three types of certificates you can create: a “dummy” certificate for testing purposes only, a self-signed certificate for a defined circle of users that trust you, and a certificate signed by an independent, publicly-known certificate authority (CA).
Creating a certificate is basically a two step process. First, a private key for the certificate authority is generated then the server certificate is signed with this key.
|For More Information|
To learn more about concepts and definitions of SSL/TSL, refer to http://httpd.apache.org/docs/2.2/ssl/ssl_intro.html.
Generating a dummy certificate is simple. Just call the script
/usr/bin/gensslcert. It creates or overwrites the
files listed below. Make use of gensslcert's
optional switches to fine-tune the certificate. Call
A copy of
ca.crt is also placed at
/srv/www/htdocs/CA.crt for download.
|For Testing Purposes Only|
A dummy certificate should never be used on a production system. Only use it for testing purposes.
If you are setting up a secure Web server for an Intranet or for a defined circle of users, it might be sufficient if you sign a certificate with your own certificate authority (CA).
Creating a self-signed certificate is an interactive nine-step process.
Change into the directory
/usr/share/doc/packages/apache2 and run the
following command: ./mkcert.sh
--no-print-directory /usr/bin/openssl /usr/sbin/
custom. Do not attempt to run this command from
outside this directory. The program provides a series of prompts, some
of which require user input.
Procedure 29.4. Creating a Self-Signed Certificate with mkcert.sh
Decide the signature algorithm used for certificates
Choose RSA (R, the default), because some older browsers have problems with DSA.
Generating RSA private key for CA (1024 bit)
No interaction needed.
Generating X.509 certificate signing request for
Create the CA's distinguished name here. This requires you to answer
a few questions, such as country name or organization name. Enter
valid data, because everything you enter here later shows up in the
certificate. You do not need to answer every question. If one does
not apply to you or you want to leave it blank, use “.”.
Common name is the name of the CA itself—choose a significant
name, such as
My company CA.
|Common Name of the CA|
The common name of the CA must be different from the server's common name, so do not choose the fully qualified hostname in this step.
Generating X.509 certificate for CA signed by
Choose certificate version 3 (the default).
Generating RSA private key for SERVER (1024 bit)
No interaction needed.
Generating X.509 certificate signing request for
Create the distinguished name for the server key here. Questions are almost identical to the ones already answered for the CA's distinguished name. The data entered here applies to the Web server and does not necessarily need to be identical to the CA's data (for example, if the server is located elsewhere).
|Selecting a Common Name|
The common name you enter here must be the fully qualified hostname of your secure server (for example, www.example.com). Otherwise the browser issues a warning that the certificate does not match the server when accessing the Web server.
Generating X.509 certificate signed by own CA
Choose certificate version 3 (the default).
Encrypting RSA private key of CA with a passphrase for
It is strongly recommended to encrypt the private key of the CA with a password, so choose Y and enter a password.
Encrypting RSA private key of SERVER with a passphrase for
Encrypting the server key with a password requires you to enter this password every time you start the Web server. This makes it difficult to automatically start the server on boot or to restart the Web server. Therefore, it is common sense to say N to this question. Keep in mind that your key is unprotected when not encrypted with a password and make sure that only authorized persons have access to the key.
|Encrypting the Server Key|
If you choose to encrypt the server key with a password, increase
the value for
The script's result page presents a list of certificates and keys it
has generated. Contrary to what the script outputs, the files have not
been generated in the local directory
conf, but to
the correct locations under
The last step is to copy the CA certificate file from
/etc/apache2/ssl.crt/ca.crt to a location where
your users can access it in order to incorporate it into the list of
known and trusted CAs in their Web browsers. Otherwise a browser
complains that the certificate was issued by an unknown authority. The
certificate is valid for one year.
Only use a self-signed certificate on a Web server that is accessed by people who know and trust you as a certificate authority. It is not recommended to use such a certificate for a public shop, for example.
There are a number of official certificate authorities that sign your certificates. The certificate is signed by a trustworthy third party, so can be fully trusted. Publicly operating secure Web servers usually have got an officially signed certificate.
The best-known official CAs are Thawte (http://www.thawte.com/) or Verisign (http://www.verisign.com). These and other CAs are already compiled into all browsers, so certificates signed by these certificate authorities are automatically accepted by the browser.
When requesting an officially signed certificate, you do not send a certificate to the CA. Instead, issue a Certificate Signing Request (CSR). To create a CSR, call the script /usr/share/ssl/misc/CA.sh -newreq.
First the script asks for a password with which the CSR should be
encrypted. Then you are asked to enter a distinguished name. This
requires you to answer a few questions, such as country name or
organization name. Enter valid data—everything you enter here
later shows up in the certificate and is checked. You do not need to
answer every question. If one does not apply to you or you want to
leave it blank, use “.”. Common name is the name of the CA
itself—choose a significant name, such as
company CA. Last, a challenge password and an alternative
company name must be entered.
Find the CSR in the directory from which you called the script. The
file is named
The default port for SSL and TLS requests on the Web server side is 443. There is no conflict between a “regular” Apache listening on port 80 and an SSL/TLS-enabled Apache listening on port 443. In fact, HTTP and HTTPS can be run with the same Apache instance. Usually separate virtual hosts are used to dispatch requests to port 80 and port 443 to separate virtual servers.
Do not forget to open the firewall for SSL-enabled Apache on port 443. This can be done with YaST as described in Section “Configuring the Firewall with YaST” (Chapter 15, Masquerading and Firewalls, ↑Security Guide).
The SSL module is enabled by default in the global server configuration.
In case it has been disabled on your host, activate it with the
following command: a2enmod ssl. To finally enable
SSL, the server needs to be started with the flag “SSL”. To
do so, call a2enflag SSL. If you have chosen to
encrypt your server certificate with a password, you should also
increase the value for
/etc/sysconfig/apache2, so you have enough time to
enter the passphrase when Apache starts. Restart the server to make
these changes active. A reload is not sufficient.
The virtual host configuration directory contains a template
SSL-specific directives that are extensively documented. Refer to
Section 18.104.22.168, “Virtual Host Configuration” for the
general virtual host configuration.
To get started, copy the template to
and edit it. Adjusting the values for the following directives should be
By default it is not possible to run multiple SSL-enabled virtual hosts on a server with only one IP address. Name-based virtual hosting requires that Apache knows which server name has been requested. The problem with SSL connections is, that such a request can only be read after the SSL connection has already been established (by using the default virtual host). As a result, users will receive a warning message stating that the certificate does not match the server name.
SUSE Linux Enterprise Server comes with an extension to the SSL protocol called Server Name Indication (SNI) addresses this issue by sending the name of the virtual domain as part of the SSL negotiation. This enables the server to “switch” to the correct virtual domain early and present the browser the correct certificate.
SNI is enabled by default on SUSE Linux Enterprise Server. In order to enable
Name-Based Virtual Hosts for SSL, configure the server as described in
Section 22.214.171.124.1, “Name-Based Virtual Hosts”
(note that you need to use port
443 rather than port
80 with SSL).
|SNI Browser Support|
SNI must also be supported on the client side. Although SNI is supported by most browsers, some browsers for mobile hardware as well as Internet Explorer and Safari on Windows* XP lack SNI support. See http://en.wikipedia.org/wiki/Server_Name_Indication for details.
Configure how to handle non-SNI capable browser with the directive
When set to
A Web server exposed to the public Internet requires an ongoing administrative effort. It is inevitable that security issues appear, both related to the software and to accidental misconfiguration. Here are some tips for how to deal with them.
If there are vulnerabilities found in the Apache software, a security advisory will be issued by SUSE. It contains instructions for fixing the vulnerabilities, which in turn should be applied as soon as possible. The SUSE security announcements are available from the following locations:
Mailing List Archive. http://lists.opensuse.org/opensuse-security-announce/
By default in SUSE Linux Enterprise Server, the
/srv/www/htdocs and the CGI directory
/srv/www/cgi-bin belong to the user and group
root. You should not change these permissions.
If the directories are writable for all, any user can place files into
them. These files might then be executed by Apache with the permissions
wwwrun, which may give the user unintended
access to file system resources. Use subdirectories of
/srv/www to place the
DocumentRoot and CGI directories for your
virtual hosts and make sure that directories and files belong to user
By default, access to the whole file system is denied in
/etc/apache2/httpd.conf. You should never overwrite
these directives, but specifically enable access to all directories
Apache should be able to read. For details, see
Section 126.96.36.199.3, “Basic Virtual Host Configuration”.
In doing so, ensure that no critical files, such as password or system
configuration files, can be read from the outside.
Interactive scripts in Perl, PHP, SSI, or any other programming language can essentially run arbitrary commands and therefore present a general security issue. Scripts that will be executed from the server should only be installed from sources the server administrator trusts—allowing users to run their own scripts is generally not a good idea. It is also recommended to do security audits for all scripts.
To make the administration of scripts as easy as possible, it is common
practice to limit the execution of CGI scripts to specific directories
instead of globally allowing them. The directives
ExecCGI are used for configuration. The SUSE Linux Enterprise Server
default configuration does not allow execution of CGI scripts from
All CGI scripts run as the same user, so different scripts can potentially conflict with each other. The module suEXEC lets you run CGI scripts under a different user and group.
When enabling user directories (with
mod_rewrite) you should strongly consider not
.htaccess files, which would allow users
to overwrite security settings. At least you should limit the user's
engagement by using the directive
AllowOverRide. In SUSE Linux Enterprise Server,
.htaccess files are enabled by default, but the
user is not allowed to overwrite any
directives when using
mod_userdir (see the
/etc/apache2/mod_userdir.conf configuration file).
If Apache does not start, the Web page is not accessible, or users cannot connect to the Web server, it is important to find the cause of the problem. Here are some typical places to look for error explanations and important things to check:
Instead of starting and stopping the Web server with the binary
/usr/sbin/httpd2, rather use the
rcapache2 script instead (described in
Section 29.3, “Starting and Stopping Apache”). It is verbose about
errors, and it even provides tips and hints for fixing configuration
In case of both fatal and nonfatal errors, check the Apache log files
for causes, mainly the error log file located at
/var/log/apache2/error_log by default.
Additionally, you can control the verbosity of the logged messages
LogLevel directive if more detail is
needed in the log files.
|A Simple Test|
Watch the Apache log messages with the command tail -F
A common mistake is to not open the ports for Apache in the firewall configuration of the server. If you configure Apache with YaST, there is a separate option available to take care of this specific issue (see Section 29.2.3, “Configuring Apache with YaST”). If you are configuring Apache manually, open firewall ports for HTTP and HTTPS via YaST's firewall module.
If the error cannot be tracked down with the help of any these, check the online Apache bug database at http://httpd.apache.org/bug_report.html. Additionally, the Apache user community can be reached via a mailing list available at http://httpd.apache.org/userslist.html. A recommended newsgroup is comp.infosystems.www.servers.unix.
apache2-doc contains the complete
Apache manual in various localizations for local installation and
reference. It is not installed by default—the quickest way to
install it is to use the command zypper in
apache2-doc. Once installed, the Apache manual is available at
http://localhost/manual/. You may also access it on
the Web at http://httpd.apache.org/docs-2.2/.
SUSE-specific configuration hints are available in the directory
For a list of new features in Apache 2.2, refer to http://httpd.apache.org/docs/2.2/new_features_2_2.html. Information about upgrading from version 2.0 to 2.2 is available at http://httpd.apache.org/docs-2.2/upgrading.html.
More information about external Apache modules that are briefly described in Section 29.4.5, “External Modules” is available at the following locations:
More information about developing Apache modules or about getting involved in the Apache Web server project are available at the following locations:
If you experience difficulties specific to Apache in SUSE Linux Enterprise Server, take a look at the Technical Information Search at http://www.novell.com/support. The history of Apache is provided at http://httpd.apache.org/ABOUT_APACHE.html. This page also explains why the server is called Apache.