Definition:
Apache HTTP Server is an open-source web server developed by the Apache Software Foundation. It receives requests over HTTP or HTTPS, locates or generates the requested resource, and sends a response to the client, usually a browser, an application, or another connected system.
The name Apache also identifies the foundation and many separate projects. In this definition it refers only to the web server, also known as Apache httpd. It should not be confused with Apache License 2.0 or with other products that use the same brand.
Índice de contenidos
Server operation
Apache listens on one or more ports and processes each HTTP request according to the active configuration. The server interprets the method, host name, path, headers, and other request data before selecting the resource or application that should respond.
A response may contain a static file, such as HTML, CSS, or an image, or output generated by an application. Apache also returns a status code, headers, and, when appropriate, a body. This separation allows it to serve websites, APIs, downloads, and other web resources.
Its architecture uses different multi-processing modules, known as MPMs, to manage connections and processes or threads. The choice between `event`, `worker`, or `prefork` depends on the operating system, loaded modules, and required compatibility.
Modular configuration
The main configuration is usually organized in files such as `httpd.conf` or `apache2.conf`, with additional files for modules, ports, and virtual hosts. Apache reads this global configuration when it starts or reloads.
Virtual hosts allow one installation to serve several domains or services. Each can define its document root, certificates, logs, access rules, and behavior. Modules extend the server with specific capabilities:
- mod_ssl adds TLS for HTTPS connections.
- mod_rewrite transforms paths through rules and conditions.
- mod_proxy forwards requests to back-end applications or servers.
- mod_headers changes request and response headers.
- mod_authz_core applies authorization rules.
In some hosting environments, Apache can also accept distributed directives through an .htaccess file. Its use depends on `AllowOverride`; when administrative access is available, the main configuration is generally more efficient and controllable.
Relationship with applications
Apache can deliver content directly or act as a reverse proxy in front of another application. In this model it manages the public connection, TLS, headers, or static files and forwards dynamic requests to processes running PHP, Python, Java, Node.js, or other technologies.
The server does not interpret all those languages by itself. Integration depends on modules, interfaces, or external services, for example PHP-FPM through FastCGI. This distinction avoids assigning Apache functions that belong to the application’s runtime environment.
It can also apply redirects, content negotiation, compression, and caching policies. These capabilities affect the technical delivery of a URL, but they do not replace development, the database, or service logic.
Administration and security
A secure installation requires keeping Apache and its modules updated, loading only necessary components, and limiting permissions. Access controls, TLS configuration, and file isolation form part of a combined defense; enabling the server alone does not protect a vulnerable application.
Access and error logs record requests, status codes, user agents, and failures. Their analysis helps diagnose problems and unusual activity, although it must follow privacy and retention policies. Common controls include:
- restricting methods, directories, and sensitive resources;
- validating certificates and TLS protocols;
- separating process and content permissions;
- reviewing modules, versions, and dependencies;
- protecting and rotating log files.
Performance and limits
Performance depends on workload, the MPM, modules, the back-end application, and infrastructure. Tuning persistent connections, compression, caching, and concurrency can improve response times, but each change should be measured in the actual environment.
Apache is known for portability, documentation, and flexibility, but there is no universally optimal configuration. Distributed rules, unnecessary modules, or a slow application can add overhead. Web performance optimization should separate server time, content generation, network transfer, and browser processing.
The official Apache HTTP Server 2.4 documentation describes available directives and modules. Consulting the documentation for the installed version is essential because a directive valid in one module or context may not be available in another.