Ozone is right, connecting to the port only verifies there is a program that is listening and bound to the port and acepting incoming connections. If your envornment normally sees crashes of those services where they server fine unless they are not running at all this may be "enough" for you. else more active tests are needed and you either need to understand the protocols that you are testing or use off the shelf modules to test functionality such as lwp for HTTP, net::ftp for FTP etc. note that this type of testing usually requires actuall access to the service (user for ftp, access to a web page to download). You need to decide what level of testing makes you comfortable.

-Waswas

In reply to Re: Re: Code Review: Checking open ports. by waswas-fng
in thread Code Review: Checking open ports. by Chady

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.