| Configuring the WSM using Device Manager |
|
The WSM sends HTTP GET or HEAD requests to HTTP servers specifying a page (identified by a URL) on the server. The WSM examines the page, compares the content of the page to user-defined content, and marks the port as either Active or Failed.
HTTP-based health checks can include the hostname for HOST: headers. If the HOST: header is required, an HTTP/1.1 GET will occur. Otherwise, an HTTP/1.0 GET will occur. An HTTP health check is successful if you get return code 200.
Note:
If content is not specified for the HTTP health check, the port being load-balanced will revert to a TCP health check.
The following examples of HTTP health checks show how the check is performed depending on the criteria you define. Virtual server service host name = everest Virtual server domain name = alteonwebsystems.com Real server group content = index.html Health check is performed using: GET /index.html HTTP/1.1 Host: everest.alteonwebsystems.com Virtual server service host name = (none) Virtual server domain name = raleighduram.cityguru.com Real server group content = /page/gen/?_template=alteon Health check is performed using: GET /page/gen/?_template=alteon HTTP/1.1 Host: raleighduram.cityguru.com Virtual server service host name = (none) Virtual server domain name = jansus Real server group content = index.html Health check is performed using: GET /index.html HTTP/1.1 Host: jansus Virtual server service host name = (none) Virtual server domain name = (none) Real server group content = index.html Health check is performed using: GET /index.html HTTP/1.0 (since no HTTP Host: header is required) Virtual server service host name = (none) Virtual server domain name = (none) Real server group content = //everest/index.html Health check is performed using: GET /index.html HTTP/1.1
Example 1:
Example 2:
Example 3:
Example 4:
Example 5:
See also:
|
|