Hi,
I am not sure but it could be due to the tie implementation of %udat wich has
also other issues and limitations.
In my login page, when I want to clean %udat I simply iterate on each value,
ex:
foreach (keys %udat) {
delete $udat{$_};
}
Regards,
Luiz Fernando B. Ribeiro
Engenho Solu��es S/C Ltda.
Em Seg 31 Mar 2003 07:40, Kaare Rasmussen escreveu:
> I have a logout.epl file with this construct:
>
> %udat = () ;
> my $prot = "http://";;
> if ($forceHttps and $ENV{HTTPS} ne 'on') {
> $prot = "https://";;
> }
> my $fn = "login.epl";
> $fn = $prot . $ENV{HTTP_HOST} . $basedir . $fn;
> $http_headers_out{'Location'} = $fn
>
> But when I reach login.epl, %udat is still fully populated. Does the
> relocation have this influence?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
