HTTP tests 🔗 link

Hi all

I've added http tests to three hosts.  Two of the hosts now have an
icon against the http test.  The third host still just has a hyphen
('-').

I don't see anything being logged on the webserver nor do I see
anything unusual on the Xymon host.

Could I get some pointers on debugging this?

Thanks

CC

-- 
RHCE#805007969328369

Ignore.  This was caused by the closing double quote on a previous
test not being there.

Thanks

On Mon, Oct 22, 2012 at 7:55 AM, Colin Coe <user-5b250cd7a540@xymon.invalid> wrote:

-- 

RHCE#805007969328369

I upgraded our xymon install from 4.3.17 to 4.3.24 and everything was
very smooth, so thank you very much!

However, I'm seeing some strange issues with http codes that worked fine
before and now throw red alarms. I have 1 server that throws a red when
checking an https url: https://server:8443/

Worked fine with .17, now throws a red 401 Unauthorized error:

https://server:8443/ - Unauthorized

HTTP/1.1 401 Unauthorized
Server: Apache-Coyote/1.1
X-FRAME-OPTIONS: SAMEORIGIN
Cache-Control: no-store, no-cache, must-revalidate, max-age=0,
post-check=0, pre-check=0
Set-Cookie: JSESSIONID=3C8BDD2EF0D9FC1D6959D8410328186B; Path=/; Secure;
HttpOnly
Cache-Control: no-store, no-cache, must-revalidate, max-age=0,
post-check=0, pre-check=0
Content-Length: 3452
Date: Wed, 03 Feb 2016 14:25:22 GMT
Connection: close

I poked around the archives and saw some random stuff regarding new http
codes, but couldn't figure out how to make this go green. Any
suggestions?

Thanks for the help!

-- 
  Matthew Daubenspeck

Gentoo Linux x86_64 Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
09:23:11 up 50 days, 9:57, 3 users, load average: 0.02, 0.02, 0.05

On 2/3/2016 5:27 AM, Matthew Daubenspeck wrote:

It is covered in the release notes:
http://sourceforge.net/projects/xymon/files/Xymon/4.3.22/

The default rules for HTTP response codes have been simplified and made more
generic:
    1xx = Warning (when the final code received)
    2xx = OK
    3xx = Warning (except 302/303/307 = OK)
    4xx = Critical
    5xx = Critical

The specific changes from previous versions are:
 - 401 and 403 response codes are now considered Critical (were OK)
 - 301 Permanent Redirect response code is now considered a Warning (was OK)
 - "Extended" or new HTTP status codes in the 4xx and 5xx range
   are now considered Critical (unknown codes were previously a Warning

If you would like a return code of 401 to return green instead of red, 
use the "httpstatus" test rather than the "http" test.

-- 
    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