in reply to damn cookies...

You don't mention it: are you sure the browsers you're testing with are actually getting the cookies? Look at the actual headers returned by your application -- I've found wsnitch to be an invaluable application for this, although if you can do so just using telnet myhost 80 and typing in the request by hand is easier. (Using LWP for this is, of course, always an option :-)

Another thing: what happens when you do something like:

my $header = $cgi->header( -type => 'text/html', -cookie => $cookie ); warn "Header sent to client:\n<<$header>>\n"; print $header;

Just so you can be absolutely certain that the browser is getting the right header. I've been bitten by this more times than I can count :-)

Chris
M-x auto-bs-mode

Replies are listed 'Best First'.
Re: Re: damn cookies...
by d_i_r_t_y (Monk) on Mar 12, 2001 at 08:31 UTC
    i did this... telnet'ed to port 80 and grep'ed the returned html by eye... the cookies were there...

    i finally nailed the problem down to the browser -- for some odd reason netscape didn't like the domain *and/or* the path arguments, since removing the domain argument made everything work out just swell.

    thanks to fpi for his/her suggestion --
    trimming back the arguments to the CGI::cookie method to just the -name and -value parameters when troubleshooting is the way to go.
    (bolded to indicate importance for the skimmers amongst us ;-) )

    d_i_r_t_y