---
title: Web Server
description: HTTP software on the server — Apache, Nginx, or LiteSpeed — that serves files and hands work to PHP.
canonical: https://penasihathosting.com/en/hosting-wiki/web-server
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# Web Server

## Overview

- **Summary:** HTTP software on the server — Apache, Nginx, or LiteSpeed — that serves files and hands work to PHP.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**A web server** is the software that accepts HTTP/HTTPS requests from browsers and returns files or script output. On hosting you most often meet **Apache**, **Nginx**, and **LiteSpeed**.

Shared plans rarely let you pick the brand — the provider does. Knowing the differences helps with migrations, caching, [`.htaccess`](/en/hosting-wiki/htaccess) expectations, and 502/504 troubleshooting. Many “slow hosting” complaints actually sit in the chain of web server, PHP, and database.

## Quick Comparison

| Server | Practical traits |
| --- | --- |
| **Apache** | Flexible, per-folder `.htaccess`, common on cPanel |
| **Nginx** | Strong for static assets and reverse proxy; centralized config |
| **LiteSpeed** | Understands many Apache rules; popular on modern shared plus cache |

There is no single “fastest” answer without context. WordPress, APIs, and large downloads need different tuning.

## How It Ties to PHP and HTTPS

The web server talks to [PHP](/en/hosting-wiki/php) through a handler (CGI, FPM, lsphp, and similar) and terminates [SSL/TLS](/en/hosting-wiki/ssl-tls). Visitors only see HTTPS pages; the stack behind them varies by host. When a page is slow, the bottleneck may be the web server, PHP, the database, or a [CDN](/en/hosting-wiki/cdn).

## What to Watch For

- `.htaccess` rules do **not** automatically apply on pure Nginx  
- Cache and compression headers may be set on the server, a CDN, or both — avoid fights  
- 502/504 errors often sit at the proxy layer (Nginx in front of PHP-FPM)  
- After migrations, retest permalinks, redirects, uploads, and admin  
- Read host docs before blaming “PHP alone”  
- Enable HTTP/2 or HTTP/3 when the host offers them and your stack is ready  

## FAQ

<Accordion>
  <AccordionItem title="Is the web server the same as hosting?">
    No. Hosting is the service and resources. The web server is software inside it (alongside databases, mail, and more).
  </AccordionItem>
  <AccordionItem title="Which is fastest?">
    It depends on workload and tuning. LiteSpeed or Nginx win certain cases; well-tuned Apache remains solid.
  </AccordionItem>
  <AccordionItem title="Should I change the web server on shared hosting?">
    Almost never. That is VPS or admin territory. On shared, focus on cache, PHP version, and CDN.
  </AccordionItem>
  <AccordionItem title="Why did the site break after Apache to Nginx?">
    Rewrite rules from `.htaccess` were not translated. Ask the host to map permalinks and redirects.
  </AccordionItem>
</Accordion>