As chromatic says, you need to display the form as one Web page, then submit it to a script that will output the cookie headers. That script will need to parse the information the user entered, then output the headers (including the cookie headers), then output the body of the Web page.

As for line endings in the headers, they are important, though whether you should use "\n" or "\r\n" may be Web server dependent (I usually use "\n", and assume my Web server will change it to a protocol-appropriate line ending). Line endings are how the Web server and browser know that one header has ended and the next has begun.

In reply to Re^3: Cookies write to screen, not to cookie file by sgifford
in thread Cookies write to screen, not to cookie file by TJD

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.