check_http issues...

[Victor Lanza]

Just wanted to say thanks and report that the fix worked perfectly. I can
pass that password without even having to escape any character.


-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Marc Powell
Sent: Monday, June 09, 2008 4:17 PM
To: nagios Mailinglist
Subject: Re: [Nagios-users] check_http issues...


On Jun 9, 2008, at 1:48 PM, Victor Lanza wrote:

> Hi all,
>
> Sooo I upgraded from 3.0.1 to 3.0.2 in the hopes that the fix for  
> the extra
> $ would be fixed in it but it doesn't seem to be.

 From http://www.nagios.org, naigos-3.0.2 was released on 5/19. The  
bug report was submitted to nagios-devel on 5/30 -
http://news.gmane.org/gmane.network.nagios.devel 
. Time travel is not (yet) permitted. ;)

You could always apply the patch yourself and try it.

--
Marc

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue. 
::: Messages without supporting info will risk being sent to /dev/null


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null