I'm not 100% sure what you're asking, but I like to do something like this:

use CGI ':standard'; my @cookies = (); push @cookies, cookie() if $test; # etc... test2() ? redirect($url) : header(-cookie => \@cookies); # go on to create the page.

It seems straightforward to me to build the header list as I go, then print the content after the headers are all printed. If I don't maintain a firewall (so to speak) between the two stages of execution, it can often get very hairy very quickly!

That said, I think that it's a good idea to use an existing and well-tested framework instead of writing everything from scratch every time. Personally, I like HTML::Mason. It's a breeze compared with writing vanilla CGI scripts.


In reply to Re: The problems of multiple CGI headers by Thelonious
in thread The problems of multiple CGI headers by bradcathey

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.