LiteSpeed ADC proxy on context level.

LiteSpeed ADC on load balancer server , 2 web servers.

Use case exmaple:

A very heavy site that user wants to separate front-end and back-end.

Front-end: https://test.litespeedtech.com/ , back-end: https://test.litespeedtech.com/admin-panel/

The goal is:

user to https://test.litespeedtech.com ---> LiteSpeed ADC ---> front-end server
user to https://test.litespeedtech.com/admin-panel/ ---> LiteSpeed ADC ---> back-end server

Both ends should use same database server and network file system.

Make sure both server are set up correctly , use local host file to bypass DNS for testing purpose.

[root@test ~]# curl http://test.litespeedtech.com
Hello World from front-end server
[root@test ~]# vi /etc/hosts
[root@test ~]# curl http://test.litespeedtech.com/admin-panel/
Hello World from back-end server
[root@test ~]#

Create 2 clusters in ADC webadmin console.

In this example they are named as front-end and back-end

And then add worker

Type choose HTTP or HTTPS , so is corresponding port to be 80 or 443. this port can be any other port as long as it works with HTTP or HTTPS, and add IP in node list.

After front-end cluster, same process for back-end cluster.

After 2 clusters are created , now create a virtual host, since only /admin-panel/ is going to be proxied to back-end , so main cluster for this domain is front-end

Now create a context.

Set URI to /admin-panel/ , please attach / at end , so every URI inside it will also be proxied, and choose back-end cluster.

Now create listener and add domain into it.

Save and restart ADC, and check the result

And access to /admin-panel/