Internet cookies are incredibly simple, but they are one of those things that have taken on a life of their own. Cookies started receiving tremendous media attention starting in February 2000 because of Internet privacy concerns, & the debate still rages.
On the other hand, cookies provide capabilities that make the Web much easier to navigate. The designers of almost every major site use them because they provide a better user experience & make it much easier to gather accurate information about the site's visitors.
We will take a look at the basic technology behind cookies, as well as some of the features they enable. You will also have the opportunity to see a real-world example of what cookies can & cannot do using a sample page.
Cookie Basics
In April of 2000 I read an in-depth article on Internet privacy in a large, respected newspaper, & that article contained a definition of cookies. Paraphrasing, the definition went like this:
Cookies are programs that web sites put on your hard disk. They sit on your computer gathering information about you & everything you do on the Internet, & whenever the web site wants to it can download all of the information the cookie has collected.
Definitions like that are fairly common in the press. The problem is, none of that information is correct. Cookies are not programs, & they cannot run like a program does. Therefore they cannot gather any information on their own. Nor can they collect any personal information about you from your machine.
Definition of a cookie:
A cookie is a piece of text that a web server can store on a user's hard disk. Cookies allow a web site to store information on a user's machine & later retrieve it. The pieces of information are stored as name-value pairs.
For example, a web site might generate a unique ID number for each visitor & store the ID number on each user's machine using a cookie file.
If you use Microsoft's Internet Explorer to browse the web, you can see all of the cookies that are stored on your machine. The most common place for them to reside is in a directory called c:\windows\cookies. When I look in that directory on my machine, I find 165 files. Each file is a text file that contains name-value pairs, & there is one file for each web site that has placed cookies on my machine.
You can see in the directory that each of these files is a simple, normal text file. You can see which web site placed the file on your machine by looking at the file name (the information is also stored inside the file). You can open each file up by clicking on it.
For example, I have visited goto.com, & the site has placed a cookie on my machine. The cookie file for goto.com contains the following information:
UserID A9A3BECE0563982D www.goto.com/
What goto.com has done is stored on my machine a single name-value pair. The name of the pair is UserID,& the value is A9A3BECE0563982D. The first time I visited goto.com, the site assigned me a unique ID value & stored it on my machine.
[Note that there probably are several other values stored in the file after the three shown above. That is housekeeping information for the browser.]
The vast majority of sites store just one piece of information -- a user ID -- on your machine. But there really is no limit -- a site can store as many name-value pairs as it likes.
A name-value pair is simply a named piece of data. It is not a program, & it cannot "do" anything. A web site can retrieve only the information that it has placed on your machine. It cannot retrieve information from other cookie files, nor any other information from your machine.
How Does Cookie Data Move?
As you saw in the previous section, cookie data is simply name-value pairs stored on your hard disk by a web site. That is all that cookie data is. The web site can store the data, & later it receives it back. A web site can only receive the data it has stored on your machine. It cannot look at any other cookie, nor can it look at anything else on your machine.
The data moves in the following manner:
If you type the URL of a web site into your browser, your browser sends a request to the web site for the page. For example, if you type the URL http://www.netcrackers.blogspot.com into your browser, your browser will contact Blogger's server & request its home page.
When the browser does this, it will look on your machine for a cookie file that Blogger has set. If it finds a Blogger cookie file, your browser will send all of the name-value pairs in the file to Blogger's server along with the URL. If it finds no cookie file, it will send no cookie data.
Blogger's web server receives the cookie data & the request for a page. If name-value pairs are received, Blogger can use them.
If no name-value pairs are received, Blogger knows that you have not visited before. The server creates a new ID for you in Blogger's database & then sends name-value pairs to your machine in the header for the web page it sends. Your machine stores the name-value pairs on your hard disk.
The web server can change name-value pairs or add new pairs whenever you visit the site & request a page.
There are other pieces of information that the server can send with the name-value pair. One of these is an expiration date. Another is a path (so that the site can associate different cookie values with different parts of the site). You have control over this process. You can set an option in your browser so that the browser informs you every time a site sends name-value pairs to you. You can then accept or deny the values.
How Do Web Sites Use Cookies?
Cookies evolved because they solve a big problem for the people who implement web sites. In the broadest sense, a cookie allows a site to store state information on your machine. This information lets a web site remember what state your browser is in. An ID is one simple piece of state information -- if an ID exists on your machine, the site knows that you have visited before. The state is, "Your browser has visited the site at least one time", & the site knows your ID from that visit.
Web sites use cookies in many different ways. Here are some of the most common examples:
Sites can accurately determine how many readers actually visit the site. It turns out that because of proxy servers, caching, concentrators & so on, the only way for a site to accurately count visitors is to set a cookie with a unique ID for each visitor. Using cookies, sites can:
->Determine how many visitors arrive
->Determine how many are new vs. repeat visitors
->Determine how often a visitor has visited
The way the site does this is by using a database. The first time a visitor arrives, the site creates a new ID in the database & sends the ID as a cookie. The next time the user comes back, the site can increment a counter associated with that ID in the database & know how many times that visitor returns.
Sites can store user preferences so that the site can look different for each visitor (often referred to as customization). For example, some sites offer you the ability to change content/layout/color. It or allows you to enter your zip code & get customized weather information.
Most sites seem to store preferences like this in the site's database & store nothing but an ID as a cookie, but storing the actual values in name-value pairs is another way to do it.
Ecommerce sites can implement things like shopping carts & "quick checkout" options. The cookie contains an ID & lets the site keep track of you as you add different things to your cart. Each item you add to your shopping cart is stored in the site's database along with your ID value. When you check out, the site knows what is in your cart by retrieving all of your selections from the database. It would be impossible to implement a convenient shopping mechanism without cookies or something like it.
In all of these examples, note that what the database is able to store is things you have selected from the site, pages you have viewed from the site, information you give to the site in online forms, etc. All of the information is stored in the site's database, & a cookie containing your unique ID is all that is stored on your computer in most cases.
An Example
To give you a simple example of what cookies & a database can do, We can take the example of Verizon.com They have created a simple history & statistics system for there articles. There system runs on the Verizon servers & lets you view your activity on the Verizon site. Here's how it works:
When you visit Verizon for the first time, the server creates a unique ID number for you & stores a cookie on your machine containing that ID. For example, on the machine I am using now, this is what I see in the Verizon cookie file:
user 35005 www.verizon.com/
There is nothing magic about the number 35,005 -- it is simply an integer that they increment each time a new visitor arrives. I was user number 35,005 to come to the Verizon site since this cookie system was installed. We could make the ID value as elaborate as we desire -- many sites use IDs containing 20 digits or more.
Now, whenever you visit any page on Verizon, your browser sends your cookie containing the ID value back to the server. The server then saves a record in the database that contains the time that you downloaded the page & the URL, along with your ID.
To see the history of your activity on Verizon, you can go to this URL on the site:
http://www.verizon.com/history.php
Your browser sends your ID value from the cookie file to the server along with the URL. The history.php page runs a piece of code that queries the database & retrieves your history on the site. It also calculates a couple of interesting statistics. Then it creates a page & sends it to your browser.
Try the URL for the history page now:
http://www.verizon.com/history.php
Then go view a couple of other pages on Verizon & try it again. You will see that the statistics change & so does the list of files.
Problems with Cookies
Cookies are not a perfect state mechanism, but they certainly make a lot of things possible that would be impossible otherwise. Here are several of the things that make cookies imperfect.
People often share machines -- Any machine that is used in a public area, & many machines used in an office environment or at home, are shared by multiple people. Let's say that you use a public machine (in a library, for example) to purchase something from an on-line store. The store will leave a cookie on the machine, & someone could later try to purchase something from the store using your account. Stores usually post large warnings about this problem, & that is why. Even so, mistakes can happen.
On something like a Windows NT machine or a UNIX machine that uses accounts properly, this is not a problem. The accounts separate all of the users' cookies. Accounts are much more relaxed in other operating systems, & it is a problem.
If you try the example above on a public machine (in a library or school, for example), & if other people using the machine have visited Verizon, then the history URL may show a very long list of files.
Cookies get erased -- If you have a problem with your browser & call tech support, probably the first thing that tech support will ask you to do is to erase all of the temporary Internet files on your machine. When you do that you lose all of your cookie files. Now when you visit a site again, that site will think you are a new user & assign you a new cookie. This tends to skew the site's record of new versus return visitors, & it also can make it hard for you to recover previously stored preferences. This is why sites ask you to register in some cases -- if you register with a user name & a password, you can re-login even if you lose your cookie file & restore your preferences. If preference values are stored directly on the machine then recovery is impossible. That is why many sites now store all user information in a central database & store only an ID value on the user's machine.
If you erase your cookie file for Verizon & then revisit the history URL in the previous section, you will find that Verizon has no history for you. The site has to create a new ID & cookie file for you, & that new ID has no data stored against it in the database.
Multiple machines -- People often use more than one machine during the day. For example a machine in the office, a machine at home & a laptop for the road. Unless the site is specifically engineered to solve the problem, the result will be three unique cookie files on all three machines. Any site that I visit from all three machines will track me as three separate users. It can be annoying to set preferences three times. Again, a site that allows registration & stores preferences centrally may make it easy for me to have the same account on three machines, but the site developers must plan for this when designing the site.If you visit the history URL demonstrated in the previous section from one machine & then try it again from another, you will find that your history lists are different. This is because the server created two IDs for you on the two machines.
There are probably not any easy solutions to these problems, short of asking users to register & storing everything in a central database.
Why the Fury around Cookies?
If you have read the article to this point, you may be wondering why there has been such an uproar in the media about cookies & Internet privacy. You have seen in this article that cookies are benign text files, & you have also seen that they provide lots of useful capabilities on the web.
There are two things that have caused the strong reaction around cookies:
- The first is something that has plagued consumers for decades but is now getting out of hand. Let's say that you purchase something from a traditional mail order catalog. The catalog company has your name, address & phone number from your order, & it also knows what items you have purchased. It can sell your information to others who might want to sell similar products to you. That is the fuel that makes telemarketing & junk mail possible.
On a web site, the site can track not only your purchases, but also the pages that you read, the ads that you click on, etc. If you then purchase something & enter your name & address, the site potentially knows much more about you than a traditional mail order company does. This makes targeting much more precise, & that makes a lot of people uncomfortable.
Different sites have different policies. Many companies have strict privacy policies & do not sell or share any personal information about customers with any third party except in cases where you specifically allow them to do so. Other companies aggregate information together & distribute it.
The second is new. There are certain infrastructure providers that can actually create cookies that are visible on multiple sites. Many firms use these companies to serve ad banners on their sites. These companies place small (1x1 pixels) GIF files on the site that allow them to load cookies on your machine. The companies can then track your movements across multiple sites. It can potentially see the search strings that you type into search engines (due more to the way some search engines implement their systems, not because anything sinister is intended). Because it can gather so much information about you from multiple sites, the companies can form very rich profiles. These are still anonymous, but they are rich.
One company then went one step further by acquiring another firm, it threatened to link these rich anonymous profiles back to name & address information -- it threatened to personalize them, & then sell the data. That began to look very much like spying to most people, & that is what caused the uproar. Some companies are in a unique position to do this sort of thing, because they serve ads on so many sites. Cross-site profiling is not a capability available to individual sites, because cookies are site specific.
