[f-nsp] Quick questions about healthcks

[Jonathan Brashear]

Minor correction:
port http status-code 200 299 

Instead of:
port http status_code 200 299


Network Engineer
> 214-981-1954 (office) 
> 214-642-4075 (cell)
> jbrashear at hq.speakeasy.net 
http://www.speakeasy.net
-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Oliver Adam
Sent: Tuesday, December 16, 2008 10:05 AM
To: Drew Weaver; 'foundry-nsp at puck.nether.net'
Subject: Re: [f-nsp] Quick questions about healthcks

What type of health check is configured? Is it the default HTTP 
health check looking like:

server real whatever a.b.c.d
   port http
   port http url "GET /something.html"

or similar?

The default return codes which are allowed are 200-299 if I remember 
correctly but you are able to influence them:


server real whatvever a.b.c.d
   port http
   port http url "GET /something.html"
   port http status_code <range1> <range2>...<range4>


port http status_code 200 299

would allow the status codes 200 to 299 only and not 404.

Regards,

Oliver

At 16:24 16.12.2008, Drew Weaver wrote:
>Content-Language: en-US
>Content-Type: multipart/alternative;
> 
>boundary="_000_B7152C470C9BF3448ED33F16A75D81C14D41690C56exchangathena_"
>
>Hi,
>
>Is there any way to make a healthck fail on a 404? For some reason 
>even though the server is returning a 404 the healthck is still passing.
>
>Thanks,
>-Drew
>
>_______________________________________________
>foundry-nsp mailing list
>foundry-nsp at puck.nether.net
>http://puck.nether.net/mailman/listinfo/foundry-nsp


_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp