[Nagiosplug-devel] RE: check_http endless redirection loop

DeBisschop, Karl kdebisschop at infoplease.com
Thu Aug 21 15:36:06 CEST 2003 

CVS HEAD fixed - simple loops will be detected and there is a maximum depth
after which redirection will be halted (both cases emit STATE_WARNING).

I plan to make redirection depth a command-line option.

Since we are nearing an alpha release on 1.4.0, I'd prefer to not backpatch
to 1.3.1, and instead focus on the upcoming alpha. If this is a critical
issue for you I will consider a backpatch, however.

--
Karl


-----Original Message-----
From: Avo Raup
To: DeBisschop, Karl
Sent: 8/18/2003 12:17 PM
Subject: check_http endless redirection loop

Hello Karl,
 
I'm writing to you as to Nagios plugin developer. I'm not a programmer
myself, more manager, and I don't know how to use common ways to issue a
request for chage, so I'm sorry for this direct email.  
 
I encountered a problem with check_http and endless redirection loop. I
found in Internet that some years ago you wrote in one mailinglist:
 
"Your experience suggests we should reconsider the default.  To follow
by default is intuitive to me, that's what a browser does. Or  we could
default to warn on redirects. But it strikes me as poor behaviour for a
monitoring tool to silently accept what actually might be an error
condition."
 
I totally agree with you. We are using Nagios and as a default behaviour
I'd prefer -f follow. (Even -f warning is better as standard -f ok.)
Especially when string check -s is included. But today I first time fall
in a endless redirection loop. Unfortunately a hosting provider of one
of our customers set up redirection to the very same place. 
 
This primer host is pillsavings4.com and redirection is pointing to the
same place. And check_http falls in a endless loop. Of course the same
happens with a browser.
 
We are using not the latest version of plugins -
nagios-plugins-1.3.0-1.i386.rpm. If this error is already debugged, I'm
very sorry for disturbing you. Please tell me, what to do? Thank you.
 
[avo]# ./check_http -H pillsavings4.com -f follow -v
Page is 622 characters
STATUS: HTTP/1.1 302 Found
**** HEADER ****
Date: Mon, 18 Aug 2003 15:57:06 GMT
Server: Apache/1.3.27 (Unix) mod_auth_passthrough/1.6 mod_log_bytes/1.2
mod_bwlimited/1.0 PHP/4.3.2 FrontPage/5.0.2.2634 mod_ssl/2.8.14
OpenSSL/0.9.6b
Location: http://pillsavings4.com/suspended.page/
<http://pillsavings4.com/suspended.page/> 
Connection: close
Content-Type: text/html; charset=iso-8859-1
**** CONTENT ****
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF=" here
<http://pillsavings4.com/suspended.page/> .

http://pillsavings4.com/suspended.page/">here</A>.<P>
<HR>
<ADDRESS>Apache/1.3.27 Server at www.pillsavings4.com
<http://www.pillsavings4.com>  Port 80</ADDRESS>
</BODY></HTML>

..... etc etc

 
Best regards
Avo Raup
Monitoring and Helpdesk
MicroLink


****************************************************************************
This email may contain confidential material.
If you were not an intended recipient, 
please notify the sender and delete all copies.
We may monitor email to and from our network.

****************************************************************************

More information about the Devel mailing list