If you check the spec, you'll notice HTTP header lines are terminated by CRLF. Your code checks for only LF. 015 is the octal value for CR, 012 is the octal value for LF. ("\r\n" isn't good cause they're not always CR and LF.)

You can tell you received two CRLF in a row when reading a line at a time by checking for a blank line.

my @headers;
{
   local $/ = "\015\012";
   while (<IN>) {
      chomp;
      last if $_ eq '';
      push(@headers, $_);
   }
}
my $request_line = shift(@headers);

[download]

That handles HTTP/1.0 and HTTP/1.1 requests, but I don't know about HTTP/0.9 requests.

In reply to Re^3: IO::Socket Get Headers by ikegami
in thread IO::Socket Get Headers by JoeJaz

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.