Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Is the protected area a subdirectory of the url you're loading in the other tab? This can cause cookies to get screwed up, because the first cookie can be set for a more specific path than the url of the second page, so a new session is started.</p> <p>This guy does a better job of explaining it:</p> <p><a href="http://www.php.net/manual/en/function.session-start.php#91298" rel="nofollow noreferrer">http://www.php.net/manual/en/function.session-start.php#91298</a></p> <blockquote> <p>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. </p> <p>Solutions: </p> <p>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. </p> <p>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?!').</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload