On 3/9/2016 8:53 AM, Shawn Heisey wrote:
- snip -
I had expected the "testip" option to force the https URL test to be
sent directly to the server, not the DNS address (which is a load
balancer), but I can see the load balancer cookie in the response and
requests in the load balancer's log.
The TESTIP controls the behavior of the CONN test. To make the HTTP test
use an IP address instead of resolving the name, use the following syntax:
http://www.sample.com=1.2.3.4/index.html
From the hosts.cfg man page:
Testing sites by IP-address
xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests.
The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites.
Instead the IP-address to connect to can be overridden by specifying it as:
http://www.sample.com=1.2.3.4/index.html
The "=1.2.3.4" will case xymonnet to run the test against the IP-address "1.2.3.4", but still trying to access a virtual website with the name "www.sample.com".
The "=ip.address.of.host" must be the last part of the hostname, so if you need to combine this with e.g. an explicit port number, it should be done as
http://www.sample.com:3128=1.2.3.4/index.html
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska