Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:proxy:start [2017/10/16 18:31]
Jackson Zhang [Control Panel environment]
+++ litespeed_wiki:proxy:start [2021/08/09 14:03] (current)
Jackson Zhang [LiteSpeed Web Server as a Proxy]
@@ Line 1: / Line 1: @@
 ====== LiteSpeed Web Server as a Proxy ======
-The purpose of a Proxy is to expand on functionality and add an extra layer of security.
+The purpose of a Proxy is to expand on functionality and add an extra layer of security. LiteSpeed 5.x and earlier version doesn't support ''ProxyPass'', ''ProxyPassReverse'' or other [[https://httpd.apache.org/docs/2.4/mod/mod_proxy.html|Apache mod_proxy]] directives. 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 set up an extra app for the proxy first, then use rewrite rules with ''[P]'', or a context to make the proxy work.
+Please note: As of LSWS v5.3.6, there is support for ProxyPass and ProxyPassMatch for an AJP backend, but not for a non-AJP backend.
+Staring from 6.x, ''ProxyPass'' and ''ProxyAddHeaders'' is supported.
+===== LiteSpeed Web Server as a Web Server HTTP Reverse 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 control panel environment, such as cpanel, you may have used Apache mod_proxy directives. LiteSpeed can work with Mod_Proxy though it does require to manually add an external app to LSWS configure to make it fully work.
+==== How Does LSWS Act as a Proxy and Handle Client Requests Meant for a Backend Server? ====
-==== 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.
-  * First the client sends a request to LiteSpeed Web Server.
+  - LSWS forwards that request to the backend server.
-  * LSWS then forwards that request to the backend server.
+  - The backend server sends a response back to LSWS.
-  * The backend server will then send a response back to LSWS.
+  - LSWS responds back to the Client acting as if there was no backend server.
-  * Finally, LSWS responds back to the Client acting as if there was no backend server.
-===== How To's =====
+==== Control Panel Environment ====
-==== Control Panel environment ====
+|[[litespeed_wiki:proxy:lsws-as-a-proxy-rewrite|How to setup Mod_Proxy like proxy on LSWS]]|Configuring LSWS + Apache Mod_Proxy in a Control Panel Environment|
-|[[litespeed_wiki:proxy:lsws-as-a-proxy-rewrite|Use mod_proxy directive with LSWS]]|How to make apache mod_proxy work with LSWS in control panel environment|
-==== LSWS native configuration ====
+==== LSWS Native Configuration as reverse proxy ====
-|[[litespeed_wiki:proxy:lsws-as-a-proxy|Proxy as a Context]]|How to setup LiteSpeed Web Server as a Proxy via Contexts|
+You can setup LSWS as a reverse proxy if you want. You can either set it up through LSWS Native virtual host contexts or rewrite rules. You can also setup LSWS as a load balancer.
-|[[litespeed_wiki:proxy:lsws-as-a-proxy-rewrite-native|Proxy as a RewriteRule in navie LSWS]]|How to setup Native LiteSpeed Web Server as a Proxy via Rewrite Rules|
+|[[litespeed_wiki:proxy:lsws-as-a-proxy|Web Proxy as a Context]]|Configuring LiteSpeed Web Server as a Proxy via Contexts|
+|[[litespeed_wiki:proxy:lsws-as-a-proxy-rewrite-native|Web Proxy as a RewriteRule in Native LSWS]]|Configuring a native LiteSpeed Web Server installation as a Proxy via Rewrite Rules|
+|[[litespeed_wiki:proxy:lsws-as-a-load-balancer|How to Set up LSWS as a Load Balancer]]|Using a series of servers for load balancing|
+===== LiteSpeed Web Server as a WebSocket Proxy =====
-Please also refer to [[litespeed_wiki:cache:no-plugin-advanced:reverse-proxy|How to setup LSWS as reverse proxy]].
+|[[litespeed_wiki:proxy:lsws-as-a-WebSocket-proxy|WebSocket Proxy]]|Configuring LiteSpeed Web Server as a WebSocket Proxy|