[Nagiosplug-help] check_http HTTP Version

[lists]

On Wed, Sep 14, 2011 at 12:49 AM, Franz, Jay <Jay.Franz at ssa.gov> wrote:
> One of the internal Web servers which we monitor recently underwent some additional hardening.  One of the hardening artifacts is that HTTP 1.0 requests are being refused, generating a 403 error.  Looking at the Web server logs, we can see that check_http is issuing a "GET / HTTP/1.0" request.  This has got to be in the FM somewhere, but I am at a loss to find it.  Is there any way to specify the HTTP version for a GET request?
>

Try using -H and supplying a host that does 1.1 requests for me...
Also what is that "$ARG1$" doing in your config?


--
<-- http://23.me.uk/2 -->
<--Time flies like an arrow; fruit flies like a banana.  -->

> Our current check_http definition and the host template which calls it follow
>
> --------------------
>
> commands.cfg:
> define command{
>        command_name    check_http
>        command_line    $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
>        }
>
> --------------------
>
> internal_host.cfg:
> define service{
>        use                             internal_host
>        host_name                       some_internal_host
>        service_description             HTTP
>        check_command                   check_http
>        }
>
> ====================
>
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>