Drew wrote:
> Steffers wrote:
> > my $header_ID=$r->header_in('sessionID');
> If you're trying to get at the cookie, this is not the way. Either use
> Apache::Cookie or CGI.pm to get the cookie contents.
>
okay. I have changd the line to the usual
my $header_ID=cookie(-name=>'sessionID');
but still no joy. If I put the .htaccess in the '/' of Apache
and then try to 'login'. The form that is generated by the
403 is the default login screen, and the form calls a cgi
underneath the '/connect/' directory. (with an .htaccess
that calls only the PerlAuthen handler)
Now from reading the logs, I can see that the authenitication
isnt being called, so fair enough, i moved the .htaccess to a
'/login/' directory, so that users will have to go there to login,
and when they hit the submit button the custom generated
form will direct them to /connect/connect.cgi
howver, all that happens now is that when i click the submit
button i get the info box of no data returned. Still using the
same code (as it were). If i run the .cgi from command line
it does output the initial welcome screen.
Hrmmm. Any ideas ? maybe my conf is all stuffed up, but
i sincerely doubt it, its a pretty vanilla conf. nothing too
radical ;)
> This code is good. But it doesn't jive with what you have above. Try
> making the first handler() actually get the cookie. Or am I missing
> something?
nope. i thought that header_in would get the cookie, and now
i understand that it would if i had 'header_in('Set-Cookie')'
(or maybe jst cookie) and then i would have to parse out the
values myself.
I jst dont understand quite what I am doing wrong. I know that i
could get standard modules and +maybe+ get the functionality
i want, but i would rather learn about Apache+perl than jst
take some code at face value.
anywayz,
many thanks for the help.
^Stefs^
