What version of MySQL is being used? I had a case of using 3.23.34 and there
apparently is a threading bug that was fixed in .35. I'd see the UPDATE command go
into the DB for the session, but it was actually never taken effect.
Bill "Elvis" Gibbs
goEbusiness.com - putting e-motion in your business
email - [EMAIL PROTECTED] work - 301-668-5090 cell - 301-748-6938
On Mon, 29 Oct 2001, Gerald Richter wrote:
> >
> > I have an authentication system that uses the Apache::Session::MySQL
> > backend with cookies to handle authentication.
> >
> > Sequence I use is:
> >
> > 1) Get username and password
> > 2) If ok, generate a sessionkey and set
> > $udat{'sessionkey'}=gen_sessionkey($username)
> >
> > However, every now and then Embperl will suddenly turn up with an old
> > value for $udat{'sessionkey'}.
> >
>
> There are two things that I could image. Either for whatever reason your
> sessions never goes into the database, in this case %udat will behave like a
> normal hash and it works as long as you hit the same child. (You will hit
> the same child as long as your KeepAliveTimeout isn't over, default 15sec).
> The other possibility is you don't have set the cookiepath, but your page
> resides in other directory, which is not under the directory which the
> cookie send.
>
> Gerald
>
> -------------------------------------------------------------
> Gerald Richter ecos electronic communication services gmbh
> Internetconnect * Webserver/-design/-datenbanken * Consulting
>
> Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
> E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
> WWW: http://www.ecos.de Fax: +49 6133 925152
> -------------------------------------------------------------
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
