Apache HTTP Server

Apache HTTP Server, often called httpd, accepts HTTP requests and produces HTTP responses. It can serve files, run content handlers, terminate TLS, and forward traffic to application backends.

The useful mental model is a modular request-processing engine. The core server handles the connection and coordinates the request. Loaded modules add capabilities at defined stages. Configuration directives decide which modules act, where they act, and which content or backend produces the response.

This model explains Apache httpd's range. One installation can host static sites, expose application handlers, enforce access rules, or work as a reverse proxy. It also explains the main operational risk: configuration from several scopes and modules can combine in ways you did not intend.

Where Apache httpd fits

Apache httpd sits between clients and content. A browser or API client connects to a listening address and port. The server selects a virtual host, maps the requested URL, applies the relevant configuration, and invokes modules or handlers. It then returns a status code, headers, and an optional body.

Common roles include:

serving HTML, images, style sheets, and downloads from a document tree;
hosting several DNS names on one server with virtual hosts;
terminating TLS with mod_ssl;
forwarding requests to application servers with mod_proxy;
adding authentication, authorization, rewriting, compression, caching, and logging through modules;
exposing server activity through a restricted mod_status endpoint.

Apache httpd is not an application runtime by itself. Dynamic content requires a handler, a gateway such as CGI or FastCGI, an embedded third-party module, or a separate application reached through a proxy.

The core, modules, and one MPM

The core contains only basic server functions. Modules provide most extended behavior. Some modules are compiled into the server. Others are dynamic shared objects loaded at startup with LoadModule.

You can inspect the active build instead of guessing:

httpd -l    # statically compiled modules
httpd -M    # loaded modules, including dynamic modules

Apache HTTP Server

Where Apache httpd fits

The core, modules, and one MPM

Relevant careers