Listener Name⇑
Description
A unique name for this listener.
DOCUMENTATION
Listeners General
Table of Contents
Listener Name | Type | IP Address | Port | Binding | Secure | Enable ZeroConf | Mapped Cluster
Type⇑
Description
The Layer 7 listener type.
An “http” listener treats requests as an HTTP Request, so it will parse the request data to use for load balancing.
A “tcp” listener will not parse request data. Only the client’s IP address and port are parsed for load balancing.
Syntax
Select from drop down list
IP Address⇑
Description
Specifies the IP of this listener. All available IP addresses are listed. IPv6 addresses are enclosed in "[ ]".
To listen on all IPv4 IP addresses, select ANY. To listen on all IPv6 IP addresses, select [ANY] IPv6. If No is selected for setting Bind IPv6 Only, selecting [ANY] IPv6 will listen on IPv4 addresses as well.
By default, LiteSpeed uses separate listeners for IPv4 and IPv6 addresses. Should the need to serve both IPv4 and IPv6 arise, separate listeners should be created for each.
Syntax
Select from drop down list
Tips
If your machine has multiple IPs on different sub-networks, you can select a specific IP to only allow traffic from the corresponding sub-network.
Port⇑
Description
Specifies the TCP port of the listener. Only the super user ("root") can use ports lower than 1024. Port 80 is the default HTTP port. Port 443 is the default HTTPS port.
Syntax
Integer number
Binding⇑
Description
Specifies which lslbd child process the listener is assigned to. Multiple child processes are spawned to take advantage of the multiple CPUs in an SMP system. Different child processes can be used to handle requests to different listeners by manually associating a listener with a process. By default, a listener is assigned to all child processes.
Syntax
Select from checkbox
Secure⇑
Description
Specifies whether this is a secure (SSL) listener. For secure listeners, additional SSL settings need to be set properly.
Syntax
Select from radio box
Enable ZeroConf⇑
Description
Use ZeroConf managed load balancing and accept traffic bound for ZeroConf enabled backends.
Syntax
Select from radio box
Tips
In order for this setting to take effect, ZeroConf must also be enabled at the server level.
Mapped Cluster⇑
Description
Specifies the cluster that the Layer 4 listener will use for load balancing. The mapped cluster must be a Layer 4 cluster, which is predefined in "Clusters" tab.
Syntax
Select from drop down list
Virtual Host Mappings⇑
Description
Specifies the relationship between the listener and virtual hosts. Listeners and virtual hosts are associated by domain names. An HTTP request will be routed to a virtual host with a matching domain name. One listener can map to multiple virtual hosts for different domain names. One virtual host can also be mapped from different listeners. One listener can allow one catchall virtual host with the domain name value "*". When there is no explicitly matched domain name in the listener's mapping, the listener will forward the request to that catchall virtual host.
Tips
Only add necessary mappings. If the listener is mapped to only one virtual host, then only set up a catchall mapping "*".
Virtual Host⇑
Description
Specifies the name of a virtual host.
Syntax
Select from drop down list
Domains⇑
Description
Specifies the mapping domain names. Domain names are case insensitive and the leading "www." will be removed. The wildcard characters "*" and "?" are allowed. "?" only represents one character. "*" represents any numbers of characters. Duplicated domain names are not allowed.
Syntax
Comma-separated list.
Example
www?.example.com
"*.mydomain.com" will match all subdomains of mydomain.com.
"*" by itself is the catchall domain and will match any unmatched domain names.
"*.mydomain.com" will match all subdomains of mydomain.com.
"*" by itself is the catchall domain and will match any unmatched domain names.
Tips
If a listener is dedicated to one virtual host, always use * for the domain name to avoid unnecessary checking. Domain names with wildcard characters (other than the catchall domain) should be avoided whenever possible.