Posted by MaKroZ on 02/17/06 05:08

On Thu, 16 Feb 2006 15:58:13 +0100, Tom Peel wrote:

> We have two PHP applications on a website. We have one user who accesses
> both applications from two browsers (Mozilla in this instance) on one PC
> at the same time, and it appears that the session variables from one
> session are turning up in the other application, leading to unexpected
> and unpredictable behaviour.
> Reading the manual, it would appear that this is a result of the
> session being stored as a cookie on the client PC.
> It would appear that we can control this behaviour by turning
> session.use_cookies TRUE or FALSE in php.ini. However we would prefer
> not to do this because of possible side effects and maintenance issues.
> The manual suggests that session data can be sent in a URL, but does
> not explain further. Can someone explain how this is done?
>
> Another idea we had is to ensure that session variables are
> application-unique. Again there is a long-term maintenance issue.
>
> Any recommendations?
>
> TIA
>
> T.

Use different session names for different applications. Default session
name is 'PHPSESSID'. See session_name() function for details.

--
nn My bookmarks:
(oo) http://www.yakutia.org
| | http://www.theisplist.com
|/\| http://www.tenpieces.com

[Back to original message]