From: Jonathan A. <jo...@sq...> - 2005-11-12 17:09:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, November 11, 2005 15:06, Arnaud Ab=E9lard wrote: >> Sure, but how to you find the username on a subsequent page? Unless >> you fancy passing the username in post/get requests, you cannot. > Maybe getting it from login.php to global from $_POST, then set the > session.name using it from there? > > The solution > >> I was thinking of was passing the session id as part of the post/get (= I >> think PHP has an option for that use_trans_sid) which will make each >> page unique to the user and should resolve the problem. The only thin= g >> I can think of being an issue is downloads. I had tested it at one po= int >> and had issues with some functions. Great, so that worked okay? >>> On another subject, i'm playing with squirrelmail, trying to make it >>> run on a zero-cookie system. I can log in without cookies, passing th= e >>> sessionid in the URL to webmail.php but once in there, i need to >>> figure a way to pass it to everylink on the page (folders, messages, >>> etc). Is there a simple way to do so? (no, adding ".SID." to every >>> link isn't pretty, and no, turning register_global on isn't either) >> session.use_trans_sid > Actually that did it. I now have a cookieless squirrelmail (almost) > running smoothly. The only trouble i still have is that the compose for= m > is logging me out when sending, i haven't had time to check it yet thou= gh. > It also fixed the concurrent sessions mixup. Excellent. I'll review it in the dev branch shortly and see about gettin= g it pushed back into stable. Probably not for the 1.4.6 release though as I'd like to test with a bunch of plugins. Do you have compose in new window set? What plugins do you have? - --=20 Jonathan Angliss <jo...@sq...> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iEYEARECAAYFAkN2IbEACgkQK4PoFPj9H3OcPgCg18AeV23hoK/aoSZ2vNidL8Oq kcwAoI0F3ORKLU54KGjd5e+JfZz06N09 =3DWSFa -----END PGP SIGNATURE----- |