Re: check_http: new force http 1.0 option
Jan Wagner <[email protected]>
| Newsgroups | gmane.network.nagios.plugins.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Leandro, thanks for coming up with thie issue. Am 13.06.2012 16:49, schrieb Leandro Piccilli: > I've upgraded to latest nagios-plugins version and since I noticed > issues with check_http on some specific servers. [...] > Basically, I do need to use the -H option due to vhost > configuration on the servers, but for some unknown reason the > servers are not happy with the request using HTTP 1.1. could you please describe your problem more verbose and hopefully provide a scenario, where it failes (for example telling us, which webserver you are checking and if you changed the default settings of the webserver the config changes). Thanks, Jan. - -- Never write mail to <[email protected]>, you have been warned! - -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ - ------END GEEK CODE BLOCK------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFP2PR29u6Dud+QFyQRAk+9AKCFf8fDq5WqWzKfrSLNzQrKorcc4wCgtisC aG4SAS1/ihkykfhLvcEK14g= =MaWV -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________________ 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