I'm nitpicking I know, but the response header can start and end with many directives...the only absolutely required one is Content-Type (and it must indeed end with two linebreaks). For example, this is perfectly legal: 
Set-Cookie: USER_COOKIE=blahblahblah; path=/; domain=.example.com
Content-Type: text/plain
Transfer-Encoding: chunked
Content-Encoding: gzip

This is my content...

[download]
Of course, if the OP is already using CGI (which he should be), then you can simply use the CGI->header() method: 
print CGI->header('text/plain');

[download]

__________
Systems development is like banging your head against a wall...
It's usually very painful, but if you're persistent, you'll get through it.

In reply to Re^3: Debugging CGI/PERL by EvanK
in thread Debugging CGI/PERL by Trihedralguy

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.