MooTools TOC Generator

hide page contents


On this page I give three functions to save, read and erase cookies. Using these functions you can manage cookies on your site

First an introduction to cookies, and a summary of document.cookie, followed by an example. Then come the three function and their explanation.


Cookies were originally invented by Netscape to give 'memory' to web servers and browsers. The HTTP protocol, which arranges for the transfer of web pages to your browser and browser requests for pages to servers, is state-less, which means that once the server has sent a page to a browser requesting it, it doesn't remember a thing about it. So if you come to the same web page a second, third, hundredth or milionth time, the server once again considers it the very first time you ever come there.

This can be annoying in a number of ways. The server cannot remember if you identified yourself when you want to access protected pages, it cannot remember your user preferences, it cannot remember anything.

Cookies were invented to solve this problem. There are another to solve it, but cookies are easy to maintain and very versatile.

How cookies work

A Cookie is nothing but a small text file that's stored in your browser. It contains some data:

As soon as you request a page from a server to which a cookie should be sent, the cookie is added to the HTTP header. Server side programs can then read out the information and decide that you have the right to view page you requested or that you want your links to be yellow on a green background.

So every time you visit the site the cookie comes from, information about you is available. This is very nice sometimes, at other times, it may somewhat endager your privacy. Fortunately more and more browsers give you the opportunity to manage your cookies(deleting the one from the big site, for example)

Cookies can be read by JavaScript too. They're mostly used for storing user preferences.


Each cookie has a name-value pair that contains the actual information. The name of the cookie is for your benefit, you will search for this name when reading out the cookie information.

If you want to read out the cookie you search for the name and see what value is attached to it. Read out this value. Of course, you yourself have to decide which values the cookie can have and to write the scripts to deal with these values.

Expiry date

Each cookie has an expiry date after which it is trashed. If you don't specify the expiry date the cookie is trashed when you close the browser. The expiry date should be in UTC(Greenwich) time.

Domain and path

Each cookie also has a domain and path. The domain tells the browser to which domain the cookie should be sent. If you don't specify it, it becomes the domain of the page that sets the cookie, in this case of this page

Please note that the purpose of the domain is to allow cookies to cross sub-domains. My cookie will not be read by because its domain is When I set the domain to, the search subdomain may also read the cookie. I cannot set the cookie domain to a domain. I'm not in, I cannot make the domain Only is allowed, in this case.

The path gives you the chance to specify a directory where the cookie is active. So if you want the cookie to be only sent to pages in the directory cgi-bin, set the path /cgi-bin. Usually the path is set to /, which means the cookie is valid thougtout the entire domain.

The script does so, so the cookies you can set on this page will be sent to any page in the domain(thougt only this page has a script that searches for the cookies and does something with them).


Cookies can be created, read and erased by JavaScript. They are accesible through the property document.cookie. Though you can treat document.cookie as if it's a string, it isn't really, and you have only access to the name-value pairs

If I want to set a cookie for this domain with a name-value pair 'thinkcookie1=valuecookie1' that expires in seven days from the moment I write this sentence I do

document.cookie = 'thinkcookie1=valuecookie1; expires=Mon, 27 Jan 2010 20:20:12 UTC; path=/'

This is a very strict syntax, don't change it! (Of course the script manages these dirty bits for you)

Also, even though it looks like I'm writting this whole string to the string document.cookie, as soon as I read it out again I only see the name-value pair name-value pair:


If I want to set another cookie, I again do:

document.cookie = 'thinkcookie2=another valuecookie; expires=Mon, 27 Jan 2010 20:20:12 UTC; path=/'

The first cookie is not overwritten , as it would when document.cookie would be a real string. Instead the second one is added to document.cookie, so if we read it out we get:

thinkcookie1=valuecookie1; thinkcookie2=another valuecookie

If I reset cookie

document.cookie = 'thinkcookie2=yet anothervalue; expires=fri, 27 Jan 2010 20:20:12 UTC; path=/'

the old cookie is overwritten and document.cookie reads

thinkcookie2=valuecookie1; thinkcookie2=yet anothervalue

To read out a cookie you have to treat document.cookie as a STRING and search for certain characters(semicolons, for instance) and for the cookie name. I will explain how to do it below.

Finally, to remove a cookie, set it to expiry date before today. The browse sees that the cookie has expired and removes it.

document.cookie = 'thinkcookie2=yet anothervalue; expires=fri, 27 Jan 2007 20:20:12 UTC; path=/'


If you're thoroughly confused by all this strange syntax, try the syntax below. You can set two cookie thinkcookie1 and thinkcookie2. Fill in the desired value in the text box.

Create cookie1
Read cookie1
Erase cookie1

Create cookie2
Read cookie2
Erase cookie2

The scripts

function createCookie(name,value,days) {

         if(days) {

                var date = new Date();


                    var expires = "; expires="+date.toGMTString();
         } else {
           expires = ""; 

  document.cookie = name + "="+ value + expires+"; path=/";

}//end function

function readCookie(name) {

        var nameEQ = name + '=';

        var ca = document.cookie.split(";");

            for(var i=0;i < ca.length;i++) {

                 var c = ca[i];

                 while(c.charAt(0) == ' ') {

                       c = c.substr(1,c.length); 

                 if(c.indexOf(nameEQ) == 0) return c.substring(nameEQ.length,c.length); 

       return null;

}//end function

function eraseCookie(name) {


}//end function


The functions are not difficult, the hardest part is creating the correct syntax for setting a cookie.


when calling createCookie() you have to give it three bits of information: the name and value of the cookie and the number of days it is to remain active.In this case the name-value pair should become namecookie=valuecookie and it should be active for 7 days


If you set the numeber of days to 0 the cookie is trashed when the user close the browser. If you set the days to a negative number the cookie is trashed immediately.

The function receives the arguments and starts doing its job.

function createCookie(name,value,days) {

First of all see if there is a 'days' value. If there isn't we don't need to do the time calculation.

if(days) {

If there is, create a new Date object containing the current date.

var date = new Date();

Now get the current Time (in milliseconds) and add the required number of days (in milliseconds). Set the time of the date to this new value, so that it now contains the date in milliseconds that the cookie should expire.


Set the variable 'expires' to this date in the UTC/GMT format required by cookie

var expires = "; expires="+date.toGMTString();

If 0 is passed to the function, expires is not set and the cookie expires when the user closes his browser.

else var expires = "";

Finally write the new cookie into document.cookie in the correct syntax.

document.cookie = name+"="+value+"; expires="+expires+"; path=/";

Cookie created.


To read out a cookie, call this function and pass the name of the cookie. Put the name in variable.First check is this variable has a value(if the cookie does not exists the variable become null, which might upset the rest of your function), then do whatever is necessary.)

var x = readCookie('thinkcookie');
if(x) {
[do something to x]

The function receives the argument and starts

function readCookie(nane) {

We're going to search for the name of the cookie, followed by an =.So create this new string and put it in nameEQ:

var nameEQ = name + "=";

Then split document.cookie on semicolons. 'ca' becomes an array containing all cookies that are set for this domain and path.

var ca = document.cookie.split(";");

Then we go through the array(so through all cookies)

for(var i=0;i < ca.length;i++) {

Set c to the cookie to be checked.

var c = ca[i];

If the first character is a space, remove it by using the substring() method. Continue doing this until the first character is not a space.

while(c.charAt(0) == ' ') {c = c.substring(1,c.length);}

Now string 'c' begins with the name of the current cookie. If this is the name of the desired cookie

if(c.indexOf(nameEQ) == 0) {

we've found what were looking for. We now only need to return the value of the cookie, which is the part of 'c' that come after 'nameEQ'. By returning this value we also end the function: mission accomplished.

if(c.indexOf(nameEQ) == 0) {return c.substring(nameEQ.length,c.length)}

If, after having gone through all cookies, we haven't found the name we're looking for, the cookie is not present. We return null.

return null;

Cookie read.


Erasing is extremely simple


Pass the name of the cookie to be erased

function eraseCookie(nme) {

and call createCookie() to set the cookie with an expiry date of one day ago.


The browser, seeing that the expiry date has passed, immediately remove the cookie.

Created by @thinkphp | You can grab the source code of this demo on Forge