Re: check_http: new force http 1.0 option

Hi Jan,

2012/6/13 Jan Wagner <[email protected]>:

> 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).

The webserver is an apache with SSL configured as a reverse proxy.
On this apache, which I cannot change the configuration, there is the following:

SSLProxyEngine on
ProxyRequests off

ProxyVia Block
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On

And we are using check_http as below:
./check_http -S -H hostname -u /path

Regards,
Leandro

------------------------------------------------------------------------------
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