So I put some warns in CGI.pm initialize_globals() to see what the status of
the world and if I iterate through %{$DefaultClass}and I had a cookie, then
$DefaultClass->{'.raw_cookies'} is still hanging around.

I imagine this is why the dosumentation preaches using Apache::Cookie
instead of CGI::Cookie, but am I the only person running into this kind of
thing? To be on the safe side I am now doing undef %{$DefaultClass} in this
function, and the world seems to work much better.

My question is: am I masking some bigger problem, or is this an oversight in
the way CGI.pm and mod_perl play together?

Thanks,
Lance


Reply via email to