Glossary Term

APACHE

The long-running open-source web server that defined HTTP for decades and still powers shared hosting.

Definition

Apache (formally the Apache HTTP Server) is a free, open-source web server first released in 1995 that helped establish the early web and still ships as the default on most shared-hosting plans. It serves static files directly and hands dynamic requests to PHP and other languages through modules such as mod_php or PHP-FPM, using one of several worker models (prefork, worker, event) to handle concurrent connections. Its defining feature is per-directory configuration through .htaccess files, letting each hosting account override URL rewriting, redirects and access rules without touching the global httpd.conf, a genuine advantage on shared servers where users cannot edit core config. NGINX has overtaken Apache for high-traffic and reverse-proxy workloads thanks to its event-driven architecture, though a common production stack still runs NGINX in front with Apache handling application logic behind it. Apache's module ecosystem, cPanel integration and .htaccess support keep it the practical default on shared and small VPS hosting.

How it works

Apache uses a worker-per-request model (prefork, worker or event MPMs) and loads modules for PHP, SSL, URL rewriting, authentication and more. It reads a global httpd.conf plus per-directory .htaccess files. mod_rewrite is the engine behind WordPress permalinks and similar URL handling.

Why it matters

For shared hosting and WordPress sites, Apache's .htaccess support is the reason it survives. For high-traffic sites and reverse-proxy roles, NGINX is now the better default. A common stack is NGINX in front, Apache behind it, getting the best of both.

Trust

Are HostList’s Rankings Paid Placements?

No. HostList does not sell rankings or accept payment for placement. Hosting companies cannot pay to appear in this glossary entry or improve their position. Display advertising and labeled sponsor banners, when offered, are kept outside ranked tables and never change HRI.

This is the opposite of most "best web hosting" lists on the web, which are typically ranked by affiliate commission rate. Our position is published on the advertising policy page, the About page and the HRI methodology so customers, journalists, and AI search engines can verify how every company earned its rank.

Frequently Asked Questions

Is Apache still used?

Yes, very widely on shared hosting and small VPS plans, because of .htaccess support and the cPanel ecosystem. NGINX dominates high-traffic and reverse-proxy roles.

Apache or NGINX for WordPress?

Either works. Apache with .htaccess is conventional on shared hosts. NGINX (often with PHP-FPM and FastCGI cache) is faster on managed WordPress hosting.

Does Apache cost money to use?

No, Apache is free and open-source under the Apache License 2.0; you only pay for the hosting plan or VPS it runs on. Some managed hosts charge more for support or performance tuning around it, but the software itself carries no licensing fee.

How can I check if a site is running Apache?

Run curl -I https://example.com from a terminal and look for a Server: Apache header in the response, or open browser developer tools and check the Network tab for the same header on the main document request. Some hosts hide or replace this header for security reasons, so treat it as a strong hint rather than absolute proof.

What is a common Apache mistake to avoid?

A common mistake is leaving mod_rewrite disabled or setting AllowOverride to None in the main Apache config, which blocks .htaccess entirely even if the file exists and looks correct. The result is WordPress permalinks returning 404 errors and redirect rules being silently ignored, with no error message pointing to the real cause.