Install necessary dependency tools and libraries, such as GCC, make, APR, APR-Util, PCRE and OpenSSL; 2. Download the Apache HTTP Server source code and decompress; 3. If the system APR version is too low, you need to manually download and move it into Apache's srclib directory; 4. Configure the compilation options, specify the installation path, enable key modules, and use built-in APR; 5. Execute make and make install to complete the compilation and installation; 6. Start the Apache service and use curl or browser to verify the default page; 7. Optionally create the systemd service file for system-level management; finally get a customizable Apache server suitable for development or learning environments, and needs to be manually upgraded.
Installing Apache (officially known as the Apache HTTP Server) from source gives you full control over the features, modules, and installation path. Here's a step-by-step guide to compile and install Apache from source on a Unix-like system (eg, Linux).

1. Install Prerequisites
Before compiling Apache, you need several tools and libraries:
- GCC compiler and make
- APR (Apache Portable Runtime) and APR-Util
- PCRE (Perl Compatible Regular Expressions)
- OpenSSL (if you want HTTPS support)
On Debian/Ubuntu:

sudo apt update sudo apt install build-essential libpcre3-dev libssl-dev
On RHEL/CentOS/Fedora:
sudo yum groupinstall "Development Tools" sudo yum install pcre-devel openssl-devel # Or on newer versions with dnf: # sudo dnf install @development-tools pcre-devel openssl-devel
2. Download Apache Source Code
Go to the Apache HTTP Server download page and get the latest stable version.

Example:
cd /tmp wget https://downloads.apache.org/httpd/httpd-2.4.61.tar.gz tar -xvzf httpd-2.4.61.tar.gz cd httpd-2.4.61
?? Note: Apache 2.4 requires APR and APR-Util to be at least version 1.4. If your system doesn't have them or has outdated versions, you must compile and install them manually.
3. Download and Install APR and APR-Util (if needed)
If your system lacks proper APR versions, download them:
cd /tmp wget https://downloads.apache.org/apr/apr-1.7.4.tar.gz wget https://downloads.apache.org/apr/apr-util-1.6.3.tar.gz tar -xvzf apr-1.7.4.tar.gz tar -xvzf apr-util-1.6.3.tar.gz # Move them into the Apache source srclib directory mv apr-1.7.4 httpd-2.4.61/srclib/apr mv apr-util-1.6.3 httpd-2.4.61/srclib/apr-util
4. Configure the Build
From the Apache source directory:
cd httpd-2.4.61
Run configure
with desired options. Common ones include:
./configure \ --prefix=/usr/local/apache2 \ --enable-so \ --enable-ssl \ --enable-rewrite \ --with-included-apr \ --with-included-apr-util \ --enable-modules=most \ --enable-mods-shared=all
Explanation:
-
--prefix
: Installation directory -
--enable-so
: Allows loading modules at runtime -
--enable-ssl
: Enables HTTPS support -
--enable-rewrite
: Enables mod_rewrite -
--with-included-apr
: Use bundled APR (if you copied them intosrclib
) -
--enable-mods-shared=all
: Compiles most modules as shared objects (recommended)
If
configure
fails, check missing dependencies and install them.
5. Compile and Install
Make sudo make install
This compiles Apache and installs it to the directory specified in --prefix
.
6. Test the Installation
Start Apache:
sudo /usr/local/apache2/bin/apachectl start
Open a browser or use curl
:
curl http://localhost
You should see the default Apache test page or "It works!" message.
Check status:
sudo /usr/local/apache2/bin/apachectl status
7. (Optional) Set Up as a Service
To manage Apache like a system service, create a systemd unit file:
sudo nano /etc/systemd/system/apache2.service
Add the following (adjust paths if needed):
[Unit] Description=Apache HTTP Server After=network.target [Service] Type=forking ExecStart=/usr/local/apache2/bin/apachectl start ExecStop=/usr/local/apache2/bin/apachectl stop ExecReload=/usr/local/apache2/bin/apachectl graceful PIDFile=/usr/local/apache2/logs/httpd.pid Restart=on-failure [Install] WantedBy=multi-user.target
Then enable and start:
sudo systemctl daemon-reexec sudo systemctl enable apache2 sudo systemctl start apache2
Common Issues
- Missing APR : Apache 2.4 won't build without APR. Either install via system package or embedded source in
srclib
. - Port 80 Permission : Running on port 80 requires root or
CAP_NET_BIND_SERVICE
. Usesudo
or change port inhttpd.conf
. - Configuration file : Localized at
/usr/local/apache2/conf/httpd.conf
. Edit to customize server behavior.
That's it. You now have Apache running from a source installation. It's flexible and ideal for custom settings, development, or learning. Just remember to manually update it when new versions are released.
Basically, compile once, use forever — until you need an upgrade.
The above is the detailed content of How to install Apache from source?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

When encountering a "ConnectionRefused" error, the most direct meaning is that the target host or service you are trying to connect to explicitly reject your request. 1. Check whether the target service is running, log in to the target machine to check the service status using systemctlstatus or psaux, and start manually if it is not started; 2. Confirm whether the port is listening correctly, use netstat or ss command to check whether the service is listening to the correct port, modify the configuration file if necessary and restart the service; 3. Firewall and security group settings may cause connection denied, check the local firewall rules and cloud platform security group configuration, and temporarily close the firewall during testing; 4. IP address or DNS resolution errors may also cause problems, use ping or

Enabling KeepAlive can significantly improve website performance, especially for pages that load multiple resources. It reduces connection overhead and speeds up page loading by keeping the browser and server connection open. If the site uses a large number of small files, has duplicate visitors, or attaches importance to performance optimization, KeepAlive should be enabled. When configuring, you need to pay attention to setting a reasonable timeout time and number of requests, and test and verify its effect. Different servers such as Apache, Nginx, etc. all have corresponding configuration methods, and you need to pay attention to compatibility issues in HTTP/2 environments.

ToenableOCSPstaplinginApache,ensureyoumeettheprerequisitesandconfigurethenecessarydirectives.First,confirmyouareusingApache2.4.1ornewerwithmod_sslenabled,OpenSSL0.9.8hornewer,andhaveavalidSSLcertificateinstalled.Next,edityourApacheSSLvirtualhostconfi

The mod_proxy_wstunnel module is the key to Apache's handling of WebSocket connections, which ensures that requests are correctly forwarded to the backend and the connection is constantly opened. 1. First enable the mod_proxy and mod_proxy_wstunnel modules, and restart the Apache service; 2. Use the ws:// or wss:// protocol when configuring VirtualHost to ensure path matching; 3. Add the RequestHeader to set Upgrade and Connection headers to support protocol switching; 4. Configure valid certificates and point to the wss:// address when using SSL/TLS; 5. Test through browser console, wscat and other tools

To improve Apache performance, optimize configuration parameters are required. 1. Adjust KeepAlive parameters: Enable MaxKeepAliveRequests and set to 500 or higher, and set KeepAliveTimeout to 2~3 seconds to reduce connection overhead. 2. Configure the MPM module: Set StartServers, MinSpareServers, MaxSpareServers and MaxClients in prefork mode; set ThreadsPerChild and MaxRequestWorkers in event or worker mode to avoid excessive load. 3. Control memory usage: based on the memory usage of a single process

Apache's default web root directory is /var/www/html in most Linux distributions. This is because the Apache server provides files from a specific document root directory. If the configuration is not customized, systems such as Ubuntu, CentOS, and Fedora use /var/www/html, while macOS (using Homebrew) is usually /usr/local/var/www, and Windows (XAMPP) is C:\xampp\htdocs; to confirm the current path, you can check the Apache configuration file such as httpd.conf or apache2.conf, or create a P with phpinfo()

To improve Apache security, we need to start from module management, permission control, SSL encryption, log monitoring, etc. 1. Close unnecessary modules such as mod_imap, mod_info, etc., and make use of the LoadModule line and restart the service to take effect; 2. Set the root directory permissions to 755 or below, restrict write permissions, and disable directory traversal and script execution in the configuration; 3. Enable HTTPS, use Let'sEncrypt certificate and disable the old version of the protocol and weak encryption suite; 4. Check the access and error logs regularly, combine fail2ban to block abnormal IP, and use IP restrictions on sensitive paths.

Enable HSTS to force browsers to access websites through HTTPS, improving security. 1. To enable HTTPS in Apache, you must first configure HTTPS, and then add Strict-Transport-Security response header in the site configuration file or .htaccess; 2. To configure max-age (such as 31536000 seconds), includeSubDomains and preload parameters; 3. Make sure that the mod_headers module is enabled, otherwise run sudoa2enmodheaders and restart Apache; 4. You can optionally submit to the HSTSPreload list, but it must satisfy that both the main site and the subdomain support HTTPS.
