By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,089 Members | 1,964 Online
Bytes IT Community
Submit an Article
Got Smarts?
Share your bits of IT knowledge by writing an article on Bytes.

PHP Sessions

Atli
Expert 5K+
P: 5,058
Introduction:
Sessions are one of the simplest and more powerful tools in a web developers arsenal. This tool is invaluable in dynamic web page development and it is one of those things every developer needs to know how to use.
This article explains the basics of PHP Sessions.

Assumptions:
Basic PHP knowledge is required (variables, arrays and such)
HTML Forms.

What are Sessions?
Sessions are a way of storing data. When developing interactive web applications we often find ourselves in need of a safe place to put certain pieces of information, such as User ID's and names. Somewhere it won’t be lost every time the browser is refreshed or redirected. This is exactly what Sessions do. They store your data on the server, so you can access it at any time, from within any server-side script.
To make this possible a file is created on the server, it is linked to a SessionID that is generated and sent to the browser as a cookie or through the URL as GET data.
Then, any time your browser is refreshed/redirected the server-side code reads this SessionID and loads the information stored in the file on the server.

Why would I use Sessions?
There are endless possible uses for this tool. It is commonly used to keep track of user information, such as Usernames and UserID's.
For example, if you take a look at the top of the Bytes page your are currently on. If you are logged in you will see a welcome message and some user controls. These fields will stay the same no matter where you go on the Bytes web. To make this possible, your user info must be stored somewhere safe, where the server-side script will be able to read it. This is the very reason Sessions exists, to make things like this possible.

How do I use Sessions?
Using Sessions in PHP is very simple. First of all, you need to tell your script that you are going to be using Sessions.
This is done by invoking the start_session() function. This function will either create a new session or re-open an existing one. Because this function needs to send header data to your browser, it must be called before any output is sent.

Once you have told your browser to use sessions, you can access your session data by calling the $_SESSION super-global. This is an array, that works pretty much like any other PHP array. You can add, edit, read and unset it's fields just like you would a normal array.

This is a little example of how to create a session and use the $_SESSION array:
Expand|Select|Wrap|Line Numbers
  1. // Start the session
  2. session_start();
  3.  
  4. // Create a session variable
  5. $_SESSION['MyVar'] = "This is my session variable";
  6.  
  7. // Use the session variable
  8. echo "MyVar: ". $_SESSION['MyVar'];
  9.  
  10. // Edit a session variable
  11. $_SESSION['MyVar'] = "I just edited my first variable";
  12.  
  13. // Delete a session variable
  14. unset($_SESSION['MyVar']);
  15.  
Once you have set a field inside the $_SESSION array, it will be available to any server-side script on the web until the browser is closed or until the field is manually unset.

A simple example:
Earlier in the article I talked about storing user data with Sessions. This little example shows how you can gather user information and store it in the PHP Session array.
It simply asks the user for a username through a HTML form and adds it to the Session. Then when the user has logged in, it prints a welcome message and gives the user the option to log out. If the user chooses to log out, it simply unsets the Session field. effectively logging the user out.
Expand|Select|Wrap|Line Numbers
  1. <?php
  2. // Start the session
  3. session_start();
  4.  
  5. // Check if a username is stored in the session
  6. if(isset($_SESSION['Username'])) 
  7. {
  8.   // Check if the user has pressed the logout link
  9.   if(isset($_GET['logout'])) 
  10.   {
  11.     // Unset the SESSION variable Username
  12.     unset($_SESSION['Username']);
  13.     echo "You have been logged out <br /> <a href='?'>Continue</a>";
  14.   }
  15.   else 
  16.   {
  17.       // Print the weclome message
  18.       $sUsername = htmlentities($_SESSION['Username']);
  19.       echo "Your are signed in as '{$sUsername}'<br /><a href='?logout=true'>Logout</a>";
  20.   }
  21. }
  22. else
  23. {
  24.   // Check If the user has posted any data
  25.   if(isset($_POST['Username'])) 
  26.   {
  27.     // Set the SESSION variable Username
  28.     $_SESSION['Username'] = $_POST['Username'];
  29.     echo "You have been logged in! <br /><a href='?'>Continue</a>";
  30.   }
  31.   else 
  32.   {
  33.     // Print the login form
  34.     echo '
  35.         <form action="?" method="post">
  36.          Username: <input name="Username" type="text" /><br />
  37.          <input type="submit" value="Login" />
  38.        </form>';
  39.   }
  40. ?>
May 10 '07 #1
Share this Article
Share on Google+
2 Comments


ifedi
P: 60
Clear, concise beginner tutorial, Atli.
My question:
How secure are php sessions? And how reliable? I do not include here a situation where the user has jeopardised private information by, say, failing to log out, and someone else now gets hold of the system (e.g. public computers).
In other words, if I have passed sensitive information into the $_SESSION array, I can just go to sleep with both eyes closed?
Keep it flowing.
Ifedi.
Feb 15 '08 #2

Atli
Expert 5K+
P: 5,058
Hi. Sorry for the delayed answer.

PHP Session can of course be hacked in a number of ways. If you intend to use them to handle sensitive data you are going to want to add an extra layer of security (or two).

A simple way to make them a little bit more secure is to obtain the IP of the user when first creating the session and matching the saved IP to the current IP. If they do not match, the session ID could have been compromised.

Having the session time-out after a few minutes is also an easy way to improve the security somewhat. The session will time-out by default after some time, but you may want to check that out in your php.ini and make sure.

There is really nothing we can do to prevent users from accessing a session left open by another user on a public computer. From the servers point of view it is still communicating with the same system. The best defense against such problems is a low time-out delay.
Mar 5 '08 #3