Two misconceptions here (one in theory, the other in implementation). Most web servers adapt fine to different newline styles, so normally this isn't a problem, but you are correct in that the "correct" newline representation wasn't accurate in the original code.

However, "\r\n" is not the way a correct newline should be represented. \n does not have a direct, portable mapping to a specific ASCII code. Instead, it's Perl's representation of a "newline", which WILL vary depending upon the OS being used. Thus, while "\r\n" will give you the desired results under Unix, it will break even more under Windows or on MacOS. If you want to be strict about your newlines, you need to use "\015\012".

In reply to Re: Re: Learning HTTP headers by Fastolfe
in thread Learning HTTP headers by Ovid

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.