LiteSpeed Web ADC FAQ

Not yet, but we are working on it.

Not yet, but we are working on it. HA WebADC will have IP fail-over set up via keepalived on Linux. If one ADC box is down, the other one will take over immediately. ADC has a keepalived manager in webAdmin. Shared IPs need to be configured via webAdmin. Fail-over works in the same way as keepalived.

There should not be any problem with multiple NICs, as long as keepalived allows it.

Data synchronization across backend nodes is not a responsibility of the ADC. ADC only takes care of its internal states. For backend nodes, you will need shared storage for files, and DB replication for databases. If DB HA is not required, you can set up multiple web nodes talking to one DB server.

For MySQL, ADC has Layer 4 mode. It is not Layer 7, hence it can not route traffic at a per-query level and it cannot split read/write.

If a rewrite rule is used to control cache behavior, it needs to be applied to the ADC. The ADC will work with our WordPress and Magento cache plugins, and will get the cache-control-related response headers set by the plugin.

Yes. The ModSec engine in LiteSpeed Web ADC is similar to the one in our web server.

For example:

www.domain.com -> load balance across 5 servers
www.domain.com/blog -> load from a separate IP (needs to preserve host headers, as the IP only responds to requests for www.domain.com)

Yes. Just define a context for the subdirectory, assign to a different cluster.

  • Admin
  • Last modified: 2017/11/07 16:58
  • by Jackson Zhang