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 Apache 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). However, you can use a few methods to achieve the same goal on LSWS. Unless the proxy is on the same server, most of time you will need to manually setup extral app for proxy first, then use rewrite rules with [P], or context to make the proxy work.

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.

How Does LSWS Act as a Proxy and Handle Client Requests Meant for a Backend Server?

  1. The client sends a request to LiteSpeed Web Server.
  2. LSWS forwards that request to the backend server.
  3. The backend server sends a response back to LSWS.
  4. 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 LSWSConfiguring LSWS + Apache Mod_Proxy in a Control Panel Environment

LSWS Native Configuration

Web Proxy as a ContextConfiguring LiteSpeed Web Server as a Proxy via Contexts
Web Proxy as a RewriteRule in Native LSWSConfiguring a native LiteSpeed Web Server installation as a Proxy via Rewrite Rules
How to Set up LSWS as a Load BalancerUsing a series of servers for load balancing
WebSocket ProxyConfiguring LiteSpeed Web Server as a WebSocket Proxy
Reverse ProxyConfiguring LSWS as Reverse Proxy
  • Admin
  • Last modified: 2019/06/05 15:03
  • by Jackson Zhang