Getting Started with PHP Session (Including Video)_PHP Tutorial

Compared with Cookie, Session is a session stored on the server side, which is relatively safe and does not have storage length limit like Cookie. This article briefly introduces the use of Session.

Since the Session is stored on the server side in the form of a text file, there is no fear of the client modifying the Session content. In fact, in the Session file on the server side, PHP automatically modifies the permissions of the Session file, retaining only system read and write permissions, and cannot be modified through ftp, so it is much safer.

For cookies, assuming we want to verify whether the user is logged in, we must save the user name and password (possibly an md5 encrypted string) in the cookie, and verify it every time the page is requested. If the username and password are stored in the database, a database query must be executed every time, causing unnecessary burden on the database. Because we can't do just one verification. Why? Because the information in the client cookie may be modified. If you store the $admin variable to indicate whether the user is logged in, when $admin is true, it means logged in, and when it is false, it means not logged in. After passing the verification for the first time, store $admin equal to true in the cookie, and there will be no need to verify next time. Yes, is this right? Wrong, if someone forges a $admin variable with a value of true, doesn't that mean he or she will immediately gain administrative rights? Very unsafe.

bkJia Video Tutorial 32: Detailed explanation of Cookie and Session in PHP5

The Session is different. The Session is stored on the server side. Remote users cannot modify the contents of the Session file. Therefore, we can simply store a $admin variable to determine whether to log in. After the first verification is passed, set the $admin value to true. , and later determine whether the value is true. If not, go to the login interface, which can reduce a lot of database operations. And it can reduce the insecurity of passing the password every time to verify the cookie (Session verification only needs to be passed once, if you do not use the SSL security protocol). Even if the password is md5 encrypted, it can be easily intercepted.

Of course, there are many advantages to using Session, such as easy control and user-defined storage (stored in the database). I won’t say much more here.

Does Session need to be set in php.ini? Generally not needed, because not everyone has the permission to modify php.ini. The default storage path of Session is the system temporary folder of the server. We can customize it and store it in our own folder. I will introduce this later. .

Start to introduce how to create a Session. Very simple, really.

Start the Session session and create a $admin variable:

PHP code
// Start Session
session_start(); 
// Declare a variable named admin and assign it a null value.​  
$_SESSION["admin"] = null;
?>

If you use Seesion, or the PHP file wants to call the Session variable, you must start it before calling the Session, using the session_start() function. You don’t need to set anything else, PHP automatically completes the creation of the Session file.

After executing this program, we can find the Session file in the system temporary folder. Generally, the file name is in the form:

sess_4c83638b3b0dbf65583181c2f89168ec,

Followed by a 32-bit encoded random string. Open it with an editor and take a look at its contents:

admin|N;
Generally, the content is structured like this:

Variable name | type: length: value; and separate each variable with a semicolon. Some can be omitted, such as length and type.

Let’s take a look at the verification procedure, assuming that the database stores the username and md5-encrypted password:

login.php

PHP code
// After the form is submitted...
$posts = $_POST;
// Clear some whitespace symbols
foreach ($posts as $key => $value) {
$posts[$key] = trim($value);
} 
$password = md5($posts["password"]);
$username = $posts["username"];

$query = "SELECT `username` FROM `user` WHERE `password` = $password AND `username` = $username"; ​ 
// Get query results
$userInfo = $DB->getRow($query);

if (!emptyempty($userInfo)) {
// When the verification is passed, start the Session
Session_start();
// Register the admin variable for successful login and assign the value true
$_SESSION["admin"] = true;
} else { 
         die("Incorrect username and password");                                                                                            } 
?>

We start the Session on the page that requires user verification to determine whether to log in:

PHP code

// Prevent global variables from causing security risks
$admin = false;
// Start the session, this step is essential
session_start(); 
// Determine whether to log in or not
if (isset($_SESSION["admin"]) && $_SESSION["admin"] === true) { 
echo "You have successfully logged in";
} else { 
// Verification failed, set $_SESSION["admin"] to false
$_SESSION["admin"] = false;
Die("You do not have permission to access");
} 
?>

Isn’t it very simple? Just think of $_SESSION as an array stored on the server side. Each variable we register is the key of the array, which is no different from using an array.

What should I do if I want to log out of the system? Just destroy the Session.

PHP code

session_start(); 
// This method is to destroy a previously registered variable
unset($_SESSION[admin]);
// This method is to destroy the entire Session file
session_destroy();
?>

Can Session set the life cycle like Cookie? Does having Session completely abandon Cookie? I would say that using Session in combination with Cookie is the most convenient.

How does Session determine the client user? It is judged by the Session ID. What is the Session ID is the file name of the Session file. The Session ID is randomly generated, so it can ensure uniqueness and randomness and ensure the security of the Session. Generally, if the Session life cycle is not set, the Session ID is stored in the memory. After closing the browser, the ID is automatically logged out. After re-requesting the page, a new Session ID is registered.

If the client does not disable cookies, the cookie plays the role of storing the Session ID and Session lifetime when starting the Session.

Let’s manually set the Session lifetime:

PHP code

session_start(); 
// Save for one day
$lifeTime = 24 * 3600;
setcookie(session_name(), session_id(), time() + $lifeTime, "/"); 
?>

In fact, Session also provides a function session_set_cookie_params(); to set the lifetime of Session. This function must be called before the session_start() function is called:

PHP code
// Save for one day
$lifeTime = 24 * 3600;
session_set_cookie_params($lifeTime);
session_start(); 
$_SESSION["admin"] = true;
?>

If the client uses IE 6.0, the session_set_cookie_params(); function will have some problems setting cookies, so we still call the setcookie function manually to create cookies.

What if the client disables cookies? There is no way, the entire life cycle is the browser process. As long as you close the browser and request the page again, you have to re-register the Session. So how do you pass the Session ID? Passed through a URL or through a hidden form, PHP will automatically send the Session ID to the URL, which looks like:

http://www.bkjia.com/PHPjc/486445.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/486445.htmlTechArticleCompared with Cookie, Session is a session stored on the server side, which is relatively safe and does not have storage length limit like Cookie. , this article briefly introduces the use of Session. Thanks to Sessi...