This is an old revision of the document!
LiteSpeed Web Server as a Proxy
The purpose of a Proxy is to expand on functionality and add an extra layer of security. LiteSpeed doesn't support ProxyPass, ProxyPassReverse and other mod_proxy directives(starting from LSWS 5.3.6, ProxyPass and-ProxyPassMatch support for AJP backend have been added but not supported for non-AJP backend).
LiteSpeed Web Server as a Web Server HTTP Proxy
This wiki explains how to set up LiteSpeed Web Server (LSWS) as a Proxy. This makes it possible to transform a URL that is usually just an IP and Port into a Fully Qualified Domain Name.
In a control panel environment, such as cPanel, you may have used Apache mod_proxy directives. LiteSpeed can read these directives as well, though an external app must be manually added for full functionality.
How Does LSWS Act as a Proxy and Handle Client Requests Meant for a Backend Server?
- The client sends a request to LiteSpeed Web Server.
- LSWS forwards that request to the backend server.
- The backend server sends a response back to LSWS.
- LSWS responds back to the Client acting as if there was no backend server.
Control Panel Environment
| How to setup Mod_Proxy like proxy on LSWS | Configuring LSWS + Apache Mod_Proxy in a Control Panel Environment |
LSWS Native Configuration
| Web Proxy as a Context | Configuring LiteSpeed Web Server as a Proxy via Contexts |
| Web Proxy as a RewriteRule in Native LSWS | Configuring a native LiteSpeed Web Server installation as a Proxy via Rewrite Rules |
| How to Set up LSWS as a Load Balancer | Using a series of servers for load balancing |
LiteSpeed Web Server as a WebSocket Proxy
| WebSocket Proxy | Configuring LiteSpeed Web Server as a WebSocket Proxy |
LiteSpeed Web Server as Reverse Proxy
| Reverse Proxy | Configuring LSWS as Reverse Proxy |