[ nagiosplug-Bugs-3588978 ] check_http "-L" output doesn't print closing anchor tag
SourceForge.net <[email protected]>
| Newsgroups | gmane.network.nagios.plugins.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #3588978, was opened at 2012-11-21 12:06 Message generated for change (Tracker Item Submitted) made by drawks You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3588978&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-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dave Rawks (drawks) Assigned to: Nobody/Anonymous (nobody) Summary: check_http "-L" output doesn't print closing anchor tag Initial Comment: Whe calling check_http if the result is a timeout or unable to open socket the closing anchor tag is not printed. This results in display corruption in the nagios web ui. $/usr/lib/nagios/plugins/check_http -H bogus -u /index.html -t 30 -L <A HREF="http://bogus/index.html" target="_blank">Name or service not known HTTP CRITICAL - Unable to open TCP socket ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3588978&group_id=29880 ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null