<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2723.2500" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>The new check_http "$Revision: 1.21 $" has
solved the multiple TCP segments problem and the double cr lf at the end of the
GET request.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>It monitors my humble wireless access-point
beautifully!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Kind regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Paul Boot.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial
size=2>--------------------------------------------------------------------------</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>On Fri, 2003-02-07 at 04:46, Paul Boot - Bateau
Knowledge wrote:<BR> > I think you have the same problem as I did. Some
embedded HTTP servers<BR> > in wireless-access points (Sitecom WL-006) and
print-servers do not<BR> > respond to HTTP GET requests sent over multiple
TCP packets. (or TCP<BR> > fragments)<BR> I have just commited a fix which
places transfers the request in one<BR> send (which does not assure that it will
be one packet).<BR> <BR> Can you test to see if this solves your problems? (use
snapshot at<BR> <A href="http://www.debisschop.net/src/nagios"
target=_NEW>http://www.debisschop.net/src/nagios</A> if you do not have CVS
tree)<BR> <BR> --<BR> Karl<BR> <BR> <BR> <BR> > Here is the bug report I just
entered:<BR> > <BR> ><BR><A
href="http://sourceforge.net/tracker/index.php?func=detail&aid=682203&group_id=29880&atid=397597"
target=_NEW>http://sourceforge.net/tracker/index.php?func=detail&aid=682203&group_id=29880&atid=397597</A><BR>
> <BR> > I have a quick and very dirty work arround.<BR> >
<BR> > Kind regards,<BR> > <BR> > PBO.<BR> > <BR>
> <BR> > <BR> > <BR> > > Can you try the same
command with the -I flag instead of -H.<BR> > > Still just a guess here,
but remember the '-H' sets the hostname,<BR> > > whereas '-I' does not.
The server should either be successful <BR> > > or give a<BR> > >
400, so it's for from a sure thing. But maybe worth a try.<BR> > <BR> >
Ok, I tried that:<BR> > <BR> > <---cut here---><---cut
here---><---cut here---><---cut<BR> > here---><---cut<BR>
> here---><---cut here---><BR> > spaehfix:/usr/local/nagios #
./libexec/check_http --verbose -H A.B.C.D<BR> > Socket timeout after 10
seconds<BR> > spaehfix:/usr/local/nagios # ./libexec/check_http --verbose -I
A.B.C.D<BR> > Socket timeout after 10 seconds<BR> >
spaehfix:/usr/local/nagios # ./libexec/check_http --verbose -I<BR> >
<FQDN_pointing_to_A.B.C.D><BR> > Socket timeout after 10 seconds<BR>
> spaehfix:/usr/local/nagios # ./libexec/check_http --verbose -H<BR> >
<FQDN_pointing_to_A.B.C.D><BR> > Socket timeout after 10 seconds<BR>
> <---cut here---><---cut here---><---cut
here---><---cut<BR> > here---><---cut<BR> >
here---><---cut here---><BR> > <BR> > and again - on the "first
Web" on that host, all combinations of<BR> > IP/FQDN,<BR> > -H/-I is
working without giving any problems.<BR> > <BR> > Any further ideas ?<BR>
> <BR> > <BR> > Kind Regards,<BR> > <BR> > Christoph
Stotz<BR> <BR></DIV></FONT></BODY></HTML>