I want to read the file into a variable and just use something like the following to set up for returning to client. 
$res->headers($header_file_content);

[download]

Then write the method, or use this one... 

# in whatever package...

package HTTP::Response;

sub headers {
    my $obj = shift;
    my $arg = shift || die "no file nor string, aborted";
    my $fh;
    {
        no warnings 'io';  # stat might be unsuccessful
        open $fh, "<", -f $arg ? $arg: \$arg;
    }
    while( <$fh>) {
        chomp;
        my ($k,$v) = split/:\s+/,$_,2;
        $obj->header(lc $k, $v);
    }
}

package whatever; # back to whatever package

[download]

...which you can pass a file name or a string containing header lines.

In reply to Re: Help building response headers for HTTP proxy request by shmem
in thread Help building response headers for HTTP proxy request by r1n0

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.