R: Handling sessions between servers?
| From: | --- | Date: | Tue, 18 Sep 2001 11:30:57 +0000 |
| Subject: | R: Handling sessions between servers? | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-67694@lists.php.net to get a copy of this message | ||
You have to pass the SID between servers and change the directory in which
you store session files to a common location.
You can pass the SID only once, after that the second server will set a
cookie...
in the first page you can put something like this <img
src="theotherserver.com/fakeimage.php?SID">
--------------------------
Federico
flagzenNO-SPAM@libero.it
--------------------------
Michael Champagne <mchampagne@capis.com> wrote in message
Pine.WNT.4.33.0109171046200.238-100000@wkstn114.capis.com...
> Is it possible to handle sessions with PHP between separate web servers?
We
> have 2 Apache servers and would like to share session data between them.
If
> we keep the session data on an NFS mounted drive -- will this work? Would
it
> be better to write custom session handlers to store session data in a
database
> accessible from both servers? It seems like this should be possible, but
I'm
> not quite sure how to go about doing it. Also, this is on 2 separate
> platforms. One is RedHat Linux 7.1 and the other server is on AIX 4.3.3.
>
> Thanks in advance for any replies,
> Mike
>
>
>
> ******************************************************************
> This communication is for informational purposes only. It is not
> intended as an offer or solicitation for the purchase or sale of
> any financial instrument or as an official confirmation of any
> transaction, unless specifically agreed otherwise. All market
> prices, data and other information are not warranted as to
> completeness or accuracy and are subject to change without
> notice. Any comments or statements made herein do not
> necessarily reflect the views or opinions of Capital Institutional
> Services, Inc. Capital Institutional Services, Inc. accepts no
> liability for any errors or omissions arising as a result of
> transmission. Use of this communication by other than intended
> recipients is prohibited.
> ******************************************************************