Implementing Apache Reverse Proxy with mod_proxy and mod_proxy_http
Learn how to configure Apache as a reverse proxy using mod_proxy and mod_proxy_http to securely route traffic to backend application servers.
Loading…
ReadMeFeed / Community knowledge
#mod-proxy
Real questions. Useful conversations. Find the people who know your stack.
Apache Reverse Proxy: mod_proxy Design and Trust Boundaries
Apache reverse proxy design using mod_proxy: disable open proxying, forward to trusted backend, preserve client IP, and validate with apachectl configtest and curl.
Decoupling Your Backend: Implementing a Reverse Proxy with Apache mod_proxy
Learn how to use Apache mod_proxy to decouple frontend clients from backend servers, enabling SSL termination and preserving client identity with X-Forwarded-For headers.
Configuring Apache as a Reverse Proxy for Backend Abstraction and Load Balancing
Learn how to implement an Apache reverse proxy using mod_proxy and mod_proxy_balancer to abstract backend servers and distribute traffic efficiently.
Fronting Apps with Apache Event MPM and mod_proxy: A Practical Edge Setup
Use Apache Event MPM and mod_proxy to offload TLS, static files, and connection management from your app server. Includes a minimal config, tuning tips, and common pitfalls.
Putting Apache in Front of Your App: A Practical Guide to mod_proxy Reverse Proxying
How to put Apache 2.4 in front of a backend app server with ProxyPass and ProxyPassReverse — including trailing-slash pitfalls, timeout tuning, forwarded headers, and the limits of mod_proxy_balancer.
Solving Backend Drift: Implementing Dynamic Load Balancing with mod_proxy
Learn how to implement zero-downtime maintenance and high availability using Apache's mod_proxy_balancer to manage backend application clusters.
AllowEncodedSlashes default change in Apache 2.4.58: impact on mod_proxy encoded‑slash forwarding
The goal is to understand how Apache 2.4.58’s new default for AllowEncodedSlashes (Off) changes the handling of URLs that contain encoded slashes when they are forwarded by mod_proxy to a backend server. With the directive now context‑sensitive and applied to all virtual hosts unless overridden, an encoded slash (%2F) is rejected unless the server explicitly
apache