Last Modified: Jul 01, 2022
Opened: May 02, 2019
-- HTTP(S) monitors configured with username and password fail to send the expected Authorization header. -- Monitors configured with an ip-dscp value send probes with an improperly encoded value in the IP header.
In either case, depending on the monitored object, the probes may be rejected, and healthy resources may fail to be marked up.
-- In-TMM monitors is enabled (via db key bigd.tmm). -- HTTP(S) monitors employing username/password are in use. or -- Monitors specifying an ip-dscp value are in use.
You can work around this issue by either disabling in-TMM monitors or, when it comes to the username/password issue, omitting the final \r\n in the send string (i.e. only specify one set of \r\n), as in the following example: send "GET /monitor HTTP/1.0\r\nHost: test.com\r\n" There is no workaround for the ip-dscp issue other than disabling in-TMM monitors.
In-TMM monitors now work correctly with the username/password or ip-dscp options.