On Thu, Oct 13, 2011 at 09:39:43AM +0200, Jörg Linge wrote:
> http://nagiosplugins.org/man/check_http
>
> Option -e
>
> -e, --expect=STRING
> Comma-delimited list of strings, at least one of them is expected in
> the first (status) line of the server response (default: HTTP/1.)
> If
Am 13.10.2011 um 09:18 schrieb Morty:
> On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
>> Isn't there some regex matching?
>
> There is. But it didn't help me in either case. check_http
> apparently does an implicit test to make sure it gets a valid response
> code such as 200. A
On Wed, Oct 12, 2011 at 11:16:17PM -0500, Frank Bulk wrote:
> Isn't there some regex matching?
There is. But it didn't help me in either case. check_http
apparently does an implicit test to make sure it gets a valid response
code such as 200. And the regex checking is in content, not headers
or
Isn't there some regex matching?
Frank
-Original Message-
From: Morty [mailto:morty+nag...@frakir.org]
Sent: Wednesday, October 12, 2011 9:46 PM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_http and other response codes
On some of our apache servers, the n
On some of our apache servers, the normal response code is 401
(authentication required) rather than 200. I'd also like to use
nagios to make sure the apache TRACE method stays disabled, with a
response code of 405. Problem: check_http returns a warning if the
response code is anything but 200.
