What are cookies and sessions, and how do they relate to each other?

Posted on

What are cookies and sessions, and how do they relate to each other? – Even if we have a good project plan and a logical concept, we will spend the majority of our time correcting errors abaout javascript and php. Furthermore, our application can run without obvious errors with JavaScript, we must use various ways to ensure that everything is operating properly. In general, there are two types of errors that you’ll encounter while doing something wrong in code: Syntax Errors and Logic Errors. To make bug fixing easier, every JavaScript error is captured with a full stack trace and the specific line of source code marked. To assist you in resolving the JavaScript error, look at the discuss below to fix problem about What are cookies and sessions, and how do they relate to each other?.

Problem :

I am trying to understand cookies and sessions professionally.
I know that when a browser connects to a server, the server “asks” the browser to “paste” a cookie with “phpsessid” in the client browser cookies folder.

Now that we have the “phpsessid”, if the client enters the server the browser sends to the server the “phpsessid” and the server takes a look at the tmp folder and if we have a match it loads back every data the user has for this client, but I am kinda confused with the process.

I will be thankful if some one can help me understand those processes of creating a session and cookies – what is happening behind the scenes.

Solution :

Let’s go through this:

Cookies and sessions are both ways to preserve the application’s state between different requests the browser makes. It’s thanks to them that, for instance, you don’t need to log in every time you request a page on StackOverflow.


Cookies are small bits of data, (maximum of 4KB long), which hold data in a key=value pairs:

name=value; name2=value2

These are set either by JavaScript, or via the server using an HTTP header.

Cookies have an expiry datetime set, example using HTTP headers:

Set-Cookie: name2=value2; Expires=Wed, 19 Jun 2021 10:18:14 GMT

Which would cause the browser to set a cookie named name2 with a value of value2, which would expire in about 9 years.

Cookies are considered highly insecure because the user can easily manipulate their content. That’s why you should always validate cookie data. Don’t assume what you get from a cookie is necessarily what you expect.

Cookies are usually used to preserve login state, where a username and a special hash are sent from the browser, and the server checks them against the database to approve access.

Cookies are also often used in sessions creation.


Sessions are slightly different. Each user gets a session ID, which is sent back to the server for validation either by cookie or by GET variable.

Sessions are usually short-lived, which makes them ideal in saving temporary state between applications. Sessions also expire once the user closes the browser.

Sessions are considered more secure than cookies because the variables themselves are kept on the server. Here’s how it works:

  1. Server opens a session (sets a cookie via HTTP header)
  2. Server sets a session variable.
  3. Client changes page
  4. Client sends all cookies, along with the session ID from step 1.
  5. Server reads session ID from cookie.
  6. Server matches session ID from a list in a database (or memory etc).
  7. Server finds a match, reads variables which are now available on $_SESSION superglobal.

If PHP does not find a match, it will start a new session, and repeat the steps from 1-7.

You can store sensitive information on a session because it is kept on the server, but be aware that the session ID can still be stolen if the user, let’s say, logged in over an insecure WiFi. (An attacker can sniff the cookies, and set it as its own, he won’t see the variables themselves, but the server will identify the attacker as the user).

That’s the gist of it. You can learn more on the PHP manual on both subjects.

Leave a Reply

Your email address will not be published. Required fields are marked *