note 91298 deleted from function.session-start by peehaa
| From: | peehaa@php.net | Date: | Fri, 09 Dec 2016 22:24:38 +0000 |
| Subject: | note 91298 deleted from function.session-start by peehaa | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-208357@lists.php.net to get a copy of this message | ||
Note Submitter: gilthans NOSPAN at gmail dot com
----
If two different files don't access the same session, it can only mean one thing: they
aren't on the same directory level.
Examples:
a) One is under https, and one is under http. (very common and annoying error)
b) One is under /, another is under /dir1, and /dir1 was first to run. The cookie created by the
session is for /dir1 and deeper only, so the other script can't read it; it sees no session so
it starts a new one.
Solutions:
1) Session start should always happen at root dir. If one of your scripts discovers user is not
logged in, for example, use session_destroy() and send him to the login in the root dir. Scripts
that use session without requiring login needs more creative solutions, like redirecting to the root
dir, setting the session, and redirecting back.
2) Use SID from page to page, instead of cookies. The upside is that this also works with
http/https. The downside is very ugly URL codes and more difficult maintainability ('which
pages links to gallery.php without using SID?!').