Not necessarily the solution, but you should be using
use strict; # and this really helps DURING development. use CGI::Carp qw(fatalsToBrowser);
I tried setting '$ENV{'QUERY_STRING'} = "test";' before the blockquote, and it printed as expected, so not sure yet why(my own ignorance, per usual, but the only way to learn) why $ENV{'QUERY_STRING'} is not being set...

update: I took your original code, and swapped
$exit_link = "$ENV{'QUERY_STRING'}"; # for $exit_link = "Perlmonks rocks.";
after a refresh it pulls up properly. So I gather that you cannot view the cookie contents the same time that you put it, and $ENV{'QUERY_STRING'} is empty(which makes sense now because there was no REQUEST).

update(2); Spelling...

In reply to Re: Cookie Problem by omega_monk
in thread Cookie Problem by Anonymous Monk

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.