Apache Webserver with NGINX Reverse Proxy Print

Apache Web Server With Reverse Proxy

What’s a Reverse Proxy, Anyway?

Here's a metaphorical explanation:

Imagine you run a busy restaurant (your server). Customers (web visitors) show up asking for different dishes (web pages). Instead of letting them walk straight into the kitchen (Apache), you place a smart host at the front (NGINX) who takes orders, decides how to handle them, and sometimes even serves quick snacks without bothering the chef.

That’s a reverse proxy: it sits in front of your web server and manages incoming requests.

Apache vs NGINX

RISP uses NGINX as a reverse proxy in front of Apache, which is still the main web server. Here’s how they tag-team:

NGINX: The Traffic Cop

• Listens on port 80/443 (HTTP/HTTPS).
• Handles static content (images, CSS, JS) super fast.
• Checks if it can serve the request directly.
• If not, it passes the request to Apache.

Apache: The Heavy Lifter

• Handles dynamic content (PHP, CGI, WordPress, etc.).
• Processes complex logic, runs scripts, talks to databases.
• Sends the response back to NGINX, which delivers it to the user.

How It Works (Simplified Flow)

1. User visits your site → NGINX catches the request.
2. Nginx checks: “Is this a static file I can serve?”
   • ✅ Yes → serves it directly (fast).
   • ❌ No → passes it to Apache.
3. Apache processes the request (e.g., runs PHP).
4. Apache sends response → NGINX delivers it to the user.

Why Use This Setup?

• Speed: NGINX is lightning-fast for static files.
• Efficiency: Apache handles the heavy stuff only when needed.
• Security: NGINX can filter requests, block bots, and throttle traffic.
• Compatibility: Apache still supports .htaccess, mod_rewrite, and legacy apps.