Anonymous Monk is
recurring refering to the bugs filed for libwww-perl in relation to blocking/nonblocking sockets as the underlying logic for HTTP::Daemon, right?
So the dirty solution is brute forcing a "Connection: close" (by using
$c->force_last_request;) after each response, effectively what HTTP/1.0 does and HTTP/1.1 should supersede, right?
A pity, as HTTP::Daemon has elaborate handling of HTTP/0.9, HTTP/1.0 and HTTP/1.1.
To aid investigation in the "what the OS does" corner, I'd like to add that I've seen this behavior on Linux/libwww-perl and Win32/libwww-perl clients. The common denominator really seems to be libwww-perl, which seems to run into these dead-locks after a number of successful requests or right away.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.