I have been given a "quest" to write a generic check to see if there is a working HTTP connection to a "responsive" HTTP server. I don't know anything about what's on the other side, just the URL.
A simple port 80 connection test is deemed "not good enough" as the port may be open, but the server hung. Also, we are behind our proxy/cache server with no possibility of being put on the "public" side. So: I have setup the following TCP Protocol test (using microsoft as an example): Name:HTTP - microsoft.com Default Port:80 Packet to receive on connect: Anything Packet to send on connect: HEAD http://www.microsoft.com/ HTTP/1.0\x0D\x0A\x0D\x0A Packet to receive as response: Contains: 200 OK Packet to send when disconnecting: Linger: off This does work and the log file looks good, although it takes 4-5 seconds. Question 1) A cmd'ed telent session with this command takes far less than a second, so why is this method so slow? Using the IP Address instead of the FQDN didn't help. Question 2) In an attempt to tell the proxy server to hit the actual server I've included the full resource URL. This means I need a new protocol for each webserver I'm looking at. Is there any way to include the host name from the check in the protocol definition as a variable so that it's truely generic? Question 3) In other TCP protocol checks, the returned data (or a portion of it) is included in the response (i.e. for FTP). That isn't happening here. What am I doing wrong? Thanks!!! Michael Shook Technical Analyst Saddle Creek Corporation 723 Joe Tamplin Industrial Blvd Macon GA 31217 478 742 8740 ext. 105 (work) 478 256 9318 (mobile) 478 742 7917 (fax) [EMAIL PROTECTED] http://www.saddlecrk.com --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
