[Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12

[SourceForge.net]

Bugs item #2082501, was opened at 2008-08-29 16:10
Message generated for change (Comment added) made by ewasser
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General plugin execution
Group: Release (specify)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Erik Wasser (ewasser)
Assigned to: Nobody/Anonymous (nobody)
Summary: check_http redirects sporadically endless in version 1.4.12

Initial Comment:
The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING".

Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources.

Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12)
Plugin Name: check_http
Plugin Commandline showing issues: see down below
Operating System: Linux
Architecture: i386, x86_64
Compiler: gcc

WORKING VERSION 1.4.11:

% ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0

This is working everytime.

DEFECT VERSION 1.4.12:

The error itself is not consistent: B-(

% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/
% ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/

As you can see the error messages shows a messed up error message (a missing '/').

I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing
too with the version 1.4.12 so I think it's not an apache problem on the other side.

Greetings and thanks for the good work.


----------------------------------------------------------------------

>Comment By: Erik Wasser (ewasser)
Date: 2008-09-01 09:21

Message:
Logged In: YES 
user_id=80027
Originator: YES

Thanks for the feedback, that's no problem at all.

I've used the .tar.gz from SourceForge.
% cd /tmp/nagios-plugins-1.4.12
% ./configure
% make
% plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H
www.taxi-blog.de -u /wordpress/ -s Impressum -t 30
option f:4
GET /wordpress/ HTTP/1.0
User-Agent: check_http/v1991 (nagios-plugins 1.4.12)
Connection: close
Host: www.taxi-blog.de:80


http://www.taxi-blog.de:80/wordpress/ is 294 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Date: Mon, 01 Sep 2008 07:12:39 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php
Location: http://www.taxi-blog.de/wordpress/
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Connection: close
**** CONTENT ****

Redirection to http://www.taxi-blog.de:80/wordpress/
GET /wordpress/ HTTP/1.0
User-Agent: check_http/v1991 (nagios-plugins 1.4.12)
Connection: close
Host: www.taxi-blog.de:80


http://www.taxi-blog.de:80/wordpress/ is 294 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Date: Mon, 01 Sep 2008 07:12:39 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php
Location: http://www.taxi-blog.de/wordpress/
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Connection: close
**** CONTENT ****

Redirection to http://www.taxi-blog.de:80/wordpress/
GET /wordpress/ HTTP/1.0
User-Agent: check_http/v1991 (nagios-plugins 1.4.12)
Connection: close
Host: www.taxi-blog.de:80

[...snipped the repeating output...]

http://www.taxi-blog.de:80/wordpress/ is 294 characters
STATUS: HTTP/1.1 301 Moved Permanently
**** HEADER ****
Date: Mon, 01 Sep 2008 07:12:42 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php
Location: http://www.taxi-blog.de/wordpress/
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Connection: close
**** CONTENT ****

HTTP WARNING - maximum redirection depth 15 exceeded -
http://www.taxi-blog.de:80wordpress/
%

I hope that will help.


----------------------------------------------------------------------

Comment By: Holger Weiss (hweiss)
Date: 2008-08-29 17:43

Message:
Logged In: YES 
user_id=759506
Originator: NO

There's no obvious change in the code between 1.4.11 and 1.4.12 which
could cause this, and so far, I can't reproduce the problem:

% check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s
Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 0.591 second response time
|time=0.590834s;;;0.000000 size=61229B;;;0

That is, the server doesn't actually redirect this URL.  Using "-u
/wordpress" without a trailing slash redirects to /wordpress/, though.  I
tried the following call 100 times in a loop and always got an OK:

% check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de
-u /wordpress/ -s Impressum -t 30
HTTP OK HTTP/1.1 200 OK - 0.761 second response time
|time=0.760912s;;;0.000000 size=61229B;;;0

So, could you please try to reproduce the problem using "--verbose" and
post the output (up to the **** CONTENT **** part)?  (It would be nice if
you could use the version compiled from the official sources for this.)

Thank you!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880