Thanks everyone for your help. I played around with the location of some of the code and some of the parameters of the cookies per your suggestions. Things seem to be behaving now. Thanks very much. --Alex
Quoting Kenneth A Graves <[EMAIL PROTECTED]>: > On Wed, 2005-06-29 at 12:10, Alex Brelsfoard wrote: >> OK, Now, my fixed code to be able to write cookies in any browser is >> as follows: >> ---------------------------------------------- >> my $cookie = $q->cookie( -name => $COOKIENAME, >> -value => $cookieContent, >> -domain => "www.wpi.edu", >> -expires => "+1h", >> -path => "/cgi-bin/Regi", >> -secure => 1 ); >> print "Set-Cookie: $cookie\n"; >> ---------------------------------------------- >> >> However, once I write the cookie this way, my cookie retrieval function no >> longer works. > > Try piece-wise changing this code. If you aren't always coming in via > https://, then you don't want -secure=>1. If you aren't always > accessing the cookie from below /cgi-bin/Regi, then you want a less > restrictive path. And if you are in a virtual host situation where the > requesting URL might not be www.wpi.edu, then you need to change the > domain. > > I'd start with eliminating (or weakening) the path and secure options > first, since they don't seem to be in the home-baked cookie you were > using earlier. > > --kag > > > > _______________________________________________ > Boston-pm mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/boston-pm > _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
