High Fellow Monks!

I am to write a perl tool to test an own Apache module. I have some mysterious problems with low-level socket.

socket(SOCK, PF_INET, SOCK_STREAM, $proto)  || die "socket: $!";
connect(SOCK, $paddr)    || die "connect: $!";

print "Host reached\n-----------------\n" ;

[download]

The connections is ok! Next comes the problem:

    send SOCK, "$lines\n",MSG_OOB ;


    $res = recv SOCK, $line,1024,MSG_OOB ;
    while ( defined($res) )
    {
        print $line ;
        $res = recv SOCK, $line,1024,MSG_OOB ;
    }

    print "Closed\n" ;
    close SOCK ;

[download]

The message is correctly submittet to the Apache server, I could check it from the acces-log and the error-log. (The last shows that our module correctly processed the incoming data.) The socket seems to close down BEFORE Apache could send back the reply....

Any ideas?

Gabaux

In reply to Low level socket question. by gabaux

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.