HTTP EDIT GLOBAL PARAMETERS
The current section details the specific properties to be configured in a layer 7 HTTP farm profile.
The vast majority of parameters that you’ll be able to configure in a HTTP/S farm, it will need a manual farm service restart 
in order to apply the changes, so a TIP message will be shown to alert the administrator that there are global parameters or backend changes that needs to restart the service through the icon before to be applied. The system administrator is able to modify whatever parameters are needed and then restart the farm service to apply all them at the same time.
By contrast with the TCP farms profile, the HTTP profile use a weight algorithm implicitly.
Additionally, every HTTP farm profile could manage several web services through the same HTTP farm, therefore one http virtual IP and port could handle more than one load balanced web service. For that reason, the “service” under a HTTP farm is a new concept in order to offer virtual host possibilities and then a list of backends will be shown for each service created.
The specific parameters for advanced HTTP/S farms are the following:
Backend connection timeout (secs). This value indicates how long the farm is going to wait for a connection to the backend in seconds. Usually, it will be the socket opening time wait. By default, this value will be set to 20 seconds.
Backend response timeout (secs). This value indicates how long the farm is going to wait for a response from the backends in seconds. By default, this value will be set to 45 seconds.
Frequency to check resurrected backends (secs). This value in seconds is the period to get out a blacklisted real server and checks if is alive. The farm will be checking the backend periodically once the real server is marked as down, regardless of whether there is a new client connection or not. By default, this value will be set to 10 seconds.
Client request timeout (secs). This value indicates how long the farm is going to wait for a client request in seconds. Once this timeout is reached without getting any data from the client, the connection will be closed. By default, this value will be set to 30 seconds.
Number of working threads. This field indicates the number of working threads in the farm.
Rewrite Location headers. If enabled, the farm is forced to modify the Location: and Content-location: headers in responses to clients. If they point to the backend itself or to the VIP (but with a different protocol) the response will be modified to show the virtual host in the request. If the option enabled and compare backends is selected then only the backend ip address is compared, this could be useful for redirecting a request to an HTTPS listener on the same server as the HTTP listener.
HTTP verbs accepted. This field indicates the operations that will be permitted to the HTTP client requests. If a not permitted verb is requested an error will be shown to the client.
Standard HTTP request. Accept only standard HTTP requests (GET, POST, HEAD).
+ extended HTTP request. Additionally allow extended HTTP requests (PUT, DELETE).
+ standard WebDAV verbs. Additionally allow standard WebDAV verbs (LOCK, UNLOCK, PROPFIND, PROPPATCH, SEARCH, MKCOL, MOVE, COPY, OPTIONS, TRACE, MKACTIVITY, CHECKOUT, MERGE, REPORT).
+ MS extensions WebDAV verbs. Additionally allow MS extensions WebDAV verbs (SUBSCRIBE, UNSUBSCRIBE, NOTIFY, BPROPFIND, BPROPPATCH, POLL, BMOVE, BCOPY, BDELETE, CONNECT).
+ MS RPC extensions verbs. Additionally allow MS RPC extensions verbs (RPC_IN_DATA, RPC_OUT_DATA).
To apply any of these options, press the Modify Button and restart the farm service.
Personalized error messages. Through the personalized error messages, the farm service is able to answer a custom message of your site when a web code error is detected from the real servers. A personalized HTML page will be shown.
Farm listener. A listener defines how the farm is going to play with the requests from the clients. The listeners available are the following.
HTTP. This listener accepts only request in plain HTTP protocol from clients.
HTTPS. This listener accepts only request in secure HTTP protocol (HTTPS) from clients. This option will configure this farm to act as SSL offloading machine.
HTTPS Certificate. The SSL certificate is only available for HTTP farm profiles with HTTPS listener enabled, and a list of certificates will be shown to be selected for the current farm. This list could be modified under the Manage::Certificates section.
SNI list. This is a available certificate list of the https farm.
Ciphers. This field is used to build a list of ciphers accepted by SSL connections in order to harden the SSL connection. In order to make use of ciphers please select one of the following options.
ALL. This item indicates that all ciphers are allowed to be managed by the HTTPS listener. This is the default setting.
HIGH security. This option set by default the ciphers:
“kEECDH+ECDSA+AES128:kEECDH+ECDSA+AES256:kEECDH+AES128:kEECDH+AES256:kEDH+AES128:kEDH+AES256:DES-CBC3-SHA:+SHA:!aNULL:!eNULL:!LOW:!kECDH:!DSS:!MD5:!EXP:!PSK:!SRP:!CAMELLIA:!SEED”
Which they’ll be enough to passthrough a A+ in ssllabs (https://www.ssllabs.com/ssltest/).
Custom security. This option allows to set your own allowed ciphers through the Customize your ciphers field. By default this value will be “DEFAULT”.
Customize your ciphers. This is the allowed customized list of ciphers that will be accepted by the SSL connection, which it’s a string in the same format as in OpenSSL ciphers.
Add service. This field is used to add a new service through the same virtual IP and port, which specify how the requests from the clients are managed and delivered. It’s mandatory to insert at least one service in order to add backends to it. Once the services are inserted, the HTTP farm core will parse every service conditions in order to match the correspondant service in each client request. Those services conditions could be determined by URL patterns, specific headers or redirection and allows to identify several web services in through the same farm. Additionally, each service provide their own backends servers. Please refer to the Edit Farm Services in order to get further information regarding the services options.
HTTP EDIT SERVICE
The services within a HTTP farm provides a content switching method to deliver several web services with different properties, backends or even persistence methods, through some deterministic conditions used by the farm core in order to match the correct service for every client request. This service definition will be used by the farm in order to determine the backends servers that could deliver the response to the client.
Every service will be tried by the HTTP farm core in priority mode and if none service is matched then the farm core will return an error. For this reason specific multiple service definitions are allowed. If no URL is defined then every request will match.
The HTTP service conditions will be determined by virtual host and/or url pattern. All of these will be explained with details below.
The service conditions and options for HTTP farms profile are shown below.
Virtual Host. This field specifies the condition determined by the domain name through the same virtual IP and port defined by a HTTP farm. In order to discard this condition just leave it empty. This field supports regular expresions in PCRE format.
Url pattern. This field allows to determine a web service regarding the URL the client is requesting through a specific URL pattern which will be syntactically checked. In order to discard this condition just leave it empty. This field supports regular expresions in PCRE format.
Virtual Host and URL pattern are used by Zen Load Balancer in order to take decisions, so if You configure a value in some of these fields, then the request will try to match in order to enter in this service, if not match, the request will try to match with the next service.
Redirect. This field behaves as a special backend, as the client request is answered by a redirect to a new URL automatically. If you configure a Redirect value then NO configure backends in this service. If Virtual Host and URL pattern match then zen sends a Location Header response to the client in order to be redirected to the configured URL.
Redirect Type. There are two options: default or append. With default option, the url is taken as an absolute host and path to redirect to. With append option, the original request path will be appended to the host and path you specified.
Cookie insertion. If defined, Zen HTTP profile will inject a cookie in each response with the appropriate backend’s key, so that even if the session table is flushed or sessions are disabled, the proper backend can be chosen. This allows for session databases to be offloaded to the client side via browser cookies. Path is the URI for the client will send the cookie. Domain is the domain for the client will send the cookie. TTL will be how many seconds the cookie will persist for. If set to 0, cookie will expire when the browser closes.
Persistence session. This parameter defines how the HTTP service is going to manage the client session and which HTTP connection field has to be controlled to maintain safe client sessions. When a type of persistence session is selected a persistence session TTL will appear.
No persistence. The farm service won’t control the client sessions and the HTTP or HTTPS requests will be free delivered to real servers.
IP – client address. The IP client address will be used to maintain the client sessions through the real servers.
BASIC – basic authentication. The HTTP basic authentication header will be used to control the client sessions.
For example, when a web page requests a basic authentication to the client a HTTP header will contain a string like the following:
HTTP/1.1 401 Authorization Required
Server: HTTPd/1.0
Date: Sat, 27 Nov 2011 10:18:15 GMT
WWW-Authenticate: Basic realm="Secure Area"
Content-Type: text/html
Content-Length: 31 |
Then the client answer with the header:
GET /private/index.html HTTP/1.1
Host: localhost
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
|
This basic authentication string is used like an ID for the session to identify the client session.
URL – a request parameter. When the session ID is sent through a GET parameter with the URL will be possible to use this option indicating the parameter name associated with the client session ID. For example, a client request like ” http://www.example.com/index.php?sid=3a5ebc944f41daa6f849f730f1 ” has be configured as shown below:
In order to configure the URL session persistence, you’ve to select this option in the Persistence Session field and then press the Modify Button. Later, two new fields will be shown:
Persistence session time to limit (TTL). This value indicates the max time of life for an inactive client session (max session age) in seconds.
Persistence session identifier. This field is the URL parameter name that will be analyzed by the farm service and will manage the client session.
PARM – a URI parameter. Another way to identify a client session is done through a URI parameter. This is a field separated by a semicolon like the following ” http://www.example.com/private.php;EFD4Y7 “
In order to configure this kind of persistence will be sufficient to select the PARM option and press the Modify Button.
COOKIE – a certain cookie. Also, you’ll be able to select a http cookie variable to maintain the client session through the COOKIE option. A cookie has to be created by the programmer into the webpage to identify the client session, for example:
GET /spec.html HTTP/1.1
Host: www.example.org
Cookie: sessionidexample=75HRSd4356SDBfrte |
With this specification, the following configuration will be needed:
After configuring this items and pressed the Modify Button on all of them, it’s needed to restart the farm service to apply the changes.
HEADER – a certain request header. A HTTP header custom field could be used to identify the client session. For example:
GET /index.html HTTP/1.1
Host: www.example.org
X-sess: 75HRSd4356SDBfrte |
With this specification, the following configuration will be needed:
After configuring this items and pressed the Modify Button on all of them, it’s needed to restart the farm service to apply the changes.
Least response. This checkbox enable an improvement of round robin algorithm. Dynamically, the load balancer establishes the connection with lower service charge.
HTTPS Backends. This checkbox indicates to the farm that the backends servers defined in the current service are using the HTTPS language and then the data will be encrypted before to be sent.
Use farmguardian to check backend servers. Checking this box will enable a more advanced monitoring state for backends and totally personalized for your own scripts for the current service. When a problem is detected by farmguardian automatically disables the real server and will be marked as blacklisted. This is an independent service so you don’t have need to restart the farm. A farmguardian server will be launched per HTTP services defined in the farm, if this option is enabled. To get more details about this service, please read the FarmGuardian section.
Move Up and Move Down. This actions move the given Service Up or Down in the Service List, this option is useful if it is required to change the priority order, note that services are evaluated in the same order that are shown.
HTTP EDIT REAL SERVERS CONFIGURATIONS
With a HTTP farm profile you’ll be able to configure the following real servers properties:
Timeout. It’s the specific value of timeout for a backend to response. This value override the global timeout farm parameter for the current backend.
Weight. It’s the weight value for the current real server. Default value 5.
With the 
Save Real Server button you’ll apply the new configuration, or you’ll be able to cancel 
the process.
Regarding to the HTTP farm profile a message with the result will be displayed and a restart action will be requested to the administrator to the changes take effect. To apply the new configuration you have to restart the farm through the restart button .
The TIP message will not disappear until the farm is restarted.
Once the real server configuration is entered, you’ll be able to edit the config throught the 
Edit button, delete the configuration with the 
Delete Real Server button, 
enable the maintenance mode for the backend in order to stop sending requests to the current server or 
disable the maintenance mode for the current backend in order to start again to send requests to the seleted server.
The server index is useful to identify the real server configuration for the current farm.
The changes of the real servers configuration for the HTTP and HTTPS profiles need a manual farm restart.