Is this a case of most Web servers catching and correcting for this, or most browsers being smart enough to handle this? I suspect the former.

And you'd be right. It pays occasionally to remember that CGI/1.x != HTTP/1.x. The data protocol a CGI script uses to send data to the web server may look like HTTP, but it's CGI. The web server should parse the script's output per the CGI specification, not HTTP, and then issue to the browser a properly-formatted HTTP response.

The real question is: Does the CGI specification mandate any specific style of newline? Beats me, but the web server (Apache in my case) seems to like any type of newline I give it.

It always generates HTTP newlines as \cM\cJ, though.

In reply to Re: (Ovid) Re: Re: Love/Hate Internet Explorer by Fastolfe
in thread Love/Hate Internet Explorer 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.