<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <TITLE>Message</TITLE> <META content="MSHTML 6.00.2900.2523" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV> <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=984533920-12012005>Greg wrote:</SPAN></FONT></DIV> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff size=2>1) We have an app server that responds to standard HTTP requests but returns type Content-Type “application/octet-stream” (not valid HTML). check_http barfs on the output. I need something almost exactly like check_http but will accept arbitrary output. Any ideas on how do to this?</FONT></DIV> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff size=2>2) I have a web application that I want to monitor the log in process. The way it works is I POST credentials to a login web page, which then sets a cookie, and sends me a redirect. The redirected web page checks the cookie and then displays some data. check_http obviously does nothing with the cookies, so that doesn't work. I need something that will return the cookie properly. A lot of the web test script frameworks don't even appear to do that. Any thoughts on how to accomplish this?</FONT></DIV></DIV> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV> <DIV><FONT face=Arial color=#0000ff size=2><SPAN class=984533920-12012005>I replied...</SPAN></FONT></DIV> <DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2>1) You should be able to do this with check_http. Just check the HTTP response code rather than the content, it works correctly for me.</FONT></SPAN></DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2>2) This is the sort of case that I wrote check_website to cope with -- where you have to do a sequence of multiple GET or POST requests, coping with redirects and cookies and parameters. I am using it here to log in to a web site, make a selection, and then log out.</FONT></SPAN></DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2>Grab a beta copy from <A href="http://www.steveshipway.org/software">http://www.steveshipway.org/software</A> in the Nagios section, and let me know how you get on with it. There are some example config files included with it to show you how to configure a test script for check_website to follow.</FONT></SPAN></DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2></FONT></SPAN> </DIV> <DIV><SPAN class=984533920-12012005><FONT face=Arial color=#0000ff size=2>Steve</FONT></SPAN></DIV> <P><FONT size=2>---<BR>Steve Shipway: ITSS, University of Auckland<BR>Email: s.shipway@auckland.ac.nz Web: <A href="http://www.steveshipway.org/">http://www.steveshipway.org/</A> <BR>** We can only discover new oceans when we have the **<BR>** courage to lose sight of the shore. **</FONT> </P></BODY></HTML>