[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] RE: multiple http test
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] RE: multiple http test
- From: "Lee Garner" <lee (at) leegarner.com>
- Date: Wed, 12 Dec 2007 07:58:56 -0800
- References: <802789653FBE7445BF7EA6181DF47BA603F65B1A (at) ALPMLVEM16.e2k.ad.ge.com> <802789653FBE7445BF7EA6181DF47BA603F65B1B (at) ALPMLVEM16.e2k.ad.ge.com> <200712120914.29891.s_aiello (at) comcast.net>
This relates so something that I've observed. There's probably a
configuration fix for it that I haven't noticed yet.
On a server with a content check, I find that if the http response is ok as
indicated by the "http" test, but the content check fails due to a server
timeout, the content check does go clear but seems to propagate up as
green. Perhaps it's just the timing of the page creation, but I know that I
once received a "recovery" alert telling me that the content check was
clear. Obviously, this isn't what I had in mind when I set up the check.
Thanks.
Lee.
On 12/12/07, s_aiello (at) comcast.net <s_aiello (at) comcast.net> wrote:
>
>
> With cont tests, if the http query is unable to be made, then the http
> test
> will be red & the cont test will be clear. So your description of the
> situation is the way that Hobbit works.
>
>