File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Servlets and the fly likes Cookies Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "Cookies" Watch "Cookies" New topic


Pratap gogireddy

Joined: Dec 03, 2011
Posts: 7
Hi friends

Where the cookies are created and stored in servlet technology?

Is the cookies created for every request?

can anyone please explain me clearly?

thanks in advance.....
Pete Nelson
Ranch Hand

Joined: Aug 30, 2010
Posts: 147

"Cookies" are an HTTP technology, more protocol than programming language. See for the gory details. Cookies live in the exchange between server & browser, tokens passed back and forth with each request & response. They only support textual data. Data in Cookies is exposed with each request & response, so it is a very bad place to store sensitive information.

Within Servlets & JSP, we use HttpSession, which encapsulates the low-end details of working with the Cookie. When using an HttpSession, only a unique identifier is passed back and forth in the Cookie, and session attributes (which can be any java object) are stored in memory by the server. These attributes are never sent with the request & response (unless you write your program to do so), so it's more secure than data in a Cookie.

Generally in Servlets & JSP, there is no need to deal directly with the Cookie. The exception is when you need to exchange simple, non-sensitive data with another web application.

In preparing for battle I have always found that plans are useless, but planning is indispensable. -- Dwight D. Eisenhower
Pratap gogireddy

Joined: Dec 03, 2011
Posts: 7
Thanks pete

But I read in the HEAD First book

HttpSession session=request.getSession();

when we call the above method Container do the following things

it creates a new HTTP session object

it generates a new Session id

it make a new COOKIE Object

it associate the Session ID with the cookie

it sets the cookie into the response header by using SET-COOKIE Header

That means we can say that the COOKIES are created by the container or web server for the stuffing the session id and sent back to the client and saved at the client side for further use.

Is this right pete? please clarify this one.

thanks in advance.

I agree. Here's the link:
subject: Cookies
It's not a secret anymore!