Thank you so much for the insight. Your thoughts are very
valuable. I'll be digging into the CookieAuth module to see what I can
see. After I look at it just a bit, it may be that I can just use
CookieAuth as it is, or with minor tweaks and a big authentication
routine. It would deny authentication
Matt Puumala wrote:
Thank you for the reply!
I am with you 100%. There are plans for the session db, and the cookie
format, all on the drawing boards, to get past "stateless http". But
I'm trying to do it stepwise, to save my sanity.
Talking about HTTP authentication, that's a good plan.
Unfor
I created a rpm for the files in DESTDIR but when I tried to install I see:
rpm -ivh mod-perl-2.0.4-rpm.rpm
error: Failed dependencies:
perl(Apache2::FunctionTable) is needed by mod-perl-2.0.4-1.noarch
perl(Apache2: StructureTable) is needed by mod-perl-2.0.4-1.noarch
perl(
Thank you for the reply!
I am with you 100%. There are plans for the session db, and the cookie
format, all on the drawing boards, to get past "stateless http". But
I'm trying to do it stepwise, to save my sanity.
So for now the question is: How do I actually prompt the user for the
passwords? My
Hi.
Without going into the details of your code, I believe that what you are bumping against
may be the very nature of HTTP.
In your scheme, you need 2 consecutive interactions with the user, and the second one
needs to be able to "remember" what the first one was.
The basic logic of HTTP goe
