Hm, that's very verbose.

What I'm not getting is: IO::Socket::INET's doc says, "IO::Socket::INET provides an object interface to creating and using sockets in the AF_INET domain" but why is it still receiving AF_INET6 stuff?

There's also IO::Socket::INET6 maintained by Shlomi Fish.

So where should be the appropriate fix/patch placed? In HTTP::Daemon (e.g. creating a separate HTTP::Daemon6)? In IO::Socket::INET (always converts things to IPv4, so sockaddr() never returns 16 bytes)? In still-lower library? This IPv4/IPv6 dichotomy is quite confusing to me.

In reply to Re^2: IO::Socket::INET's sockaddr() returns 16 byte instead of 4, Socket::inet_ntoa() complains by sedusedan
in thread IO::Socket::INET's sockaddr() returns 16 byte instead of 4, Socket::inet_ntoa() complains by Anonymous Monk

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.