[Nagiosplug-devel] [ nagiosplug-Bugs-1457726 ] check_http -k parameters

[SourceForge.net]

Bugs item #1457726, was opened at 2006-03-24 14:22
Message generated for change (Comment added) made by gmueller_2000
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1457726&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: Argument proccessing
Group: CVS
Status: Open
Resolution: None
Priority: 5
Submitted By: Gerd Mueller (gmueller_2000)
Assigned to: Ton Voon (tonvoon)
Summary: check_http -k parameters

Initial Comment:
I found a problem with check_http. The usage told me 
to use a semicolon for -k to separate other tags to 
be sent in http header. But how can I configured that 
inside Nagios? A comment always starts with a 
semicolon always and so Nagios removes everything 
starting with the semicolon per line.

The possible solutions I see are escaping semicolons 
or use a different INPUT_DELIMITER

Gerd 

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

>Comment By: Gerd Mueller (gmueller_2000)
Date: 2006-03-24 15:07

Message:
Logged In: YES 
user_id=685055

Hi Ton,

yes, but it will not work with the current stable nagios 
release. So -k for more than one header is not useable. 
That is why I am calling it a bug.

Escaping of semicolons or escaping of all nasty characters 
inside nagios and nrpe would be also my preferred solution. 
I had a lot of problems with backslashes as well. But I 
think that will cause a lot of side-effects and won't be a 
easy patch for nagios. It might also cause a lot of 
problems with working configs. That is why I do not expect 
a change in Nagios logic before version 3. But I hope Ethan 
will consider this change for the next upcoming major 
release. Meanwhile no plugin should use a semicolon as 
parameter.

Gerd


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

Comment By: Ton Voon (tonvoon)
Date: 2006-03-24 14:51

Message:
Logged In: YES 
user_id=664364

Gerd,

This doesn't sound like a plugin problem. I'm guessing we use semi-colons 
for the delimiter because colons could be used in the data, so I'm not too 
keen on changing.

I think this is really a problem in Nagios to allow semi-colons to be escaped 
in the command that it runs.

Ton

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

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