No that's the whole point of the sample code. Try to read() CONTENT_LENGTH bytes - it will hang as read() is never returning 0/undef but is just blocking.

The only way I found to make it work was to use this:

if ( $length ) { print "Expecting $length bytes\n"; while ( length($data) < $length ) { last unless sysread( STDIN, $buf, 16 ); print "Got: $buf\n"; $data .= $buf; } }

If you use a standard read() it will hang (buffered) but sysread bypasses the buffering and it works as expected. The length check effectively avoids the last read where even for sysread it will block if there is no data left.

I will hack it into shape when I get a moment. It is good to have a failure test case in such a small portable package.....

cheers

tachyon


In reply to Re: Re: Re: Re: Re: Re: Re: Re: Re: using CGI on HTTP::Request from HTTP::Daemon by tachyon
in thread using CGI on HTTP::Request from HTTP::Daemon by gregor-e

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.