This is an old revision of the document!
Setting up a Proxy on the LiteSpeed Web ADC Context Level
Requirements
- LiteSpeed Web ADC on a load balancer server
- Two web servers.
Use Case Example
You have a very heavy site, and so you want to lighten the load by hosting the front-end and back-end on different servers.
- Front-end:
https://test.example.com/
- Back-end:
https://test.example.com/admin-panel/
The goal is:
- user requests
https://test.example.com
---> LiteSpeed ADC ---> front-end server - user requests
https://test.example.com/admin-panel/
---> LiteSpeed ADC ---> back-end server
Both ends should use same database server and network file system.
Configuration
Step 1
Make sure both servers are set up correctly. Use local host file to bypass DNS for testing purposes.
[root@test ~]# curl http://test.example.com Hello World from front-end server [root@test ~]# vi /etc/hosts [root@test ~]# curl http://test.example.com/admin-panel/ Hello World from back-end server [root@test ~]#
Step 2
Create two clusters in ADC WebAdmin console.
In this example they are named front-end
and back-end
.
Add a worker for each cluster.
For Type, choose HTTP
or HTTPS
, and the corresponding port will be set to 80 or 443, respectively. You can override the port numbers, as long as your choice works with HTTP or HTTPS as needed.
Add the IP address to Node Address List.
Step 3
After the two clusters are created, add a new virtual host. Only /admin-panel/
is going to be proxied to back-end
, so the Default Cluster for this domain is front-end
.
Create a context.
Set URI to /admin-panel/
, making sure to include the /
at the end. This ensures so every URI in that path will also be proxied.
Set Cluster to back-end
.