Cookies
Cookies
Interaction: Cookies
User server
interaction:cookies
● Think of an HTTP server like a restaurant that serves many customers. It takes
orders from them but doesn't remember who they are once they leave. This is what
we mean by "stateless" - it doesn't retain any memory of past interactions. Now,
imagine you want the restaurant to remember you so that next time you visit, it
knows your favorite dish or where you prefer to sit. That's where cookies come in.
● So, when you visit a website, it can give your browser a cookie, which is a small
piece of data. The next time you visit, your browser sends that cookie back to the
website. This helps the website remember who you are and personalize your
experience, like showing you relevant content or keeping you logged in.
Alright, let's break down how cookies work using the example with
Susan and Amazon:
01 02
Cookie Header in HTTP Response Cookie File on User's End
Message System
03 04
Cookie Header in HTTP Back-end Database at
Request Message the Web Site
1.Cookie Header in HTTP Response Message:
The "Cookie" header in the HTTP response message is used by the server to send a cookie
to the client's browser. This header contains the information about the cookie, including its
name, value, expiration date, domain, and path.
However, while cookies offer benefits in terms of convenience and customization, they also
raise privacy concerns. The extensive tracking capabilities they afford can potentially
infringe upon users' privacy by enabling the collection and sharing of sensitive information
without their explicit consent.
Thank you
-SHREYA GORE (1JS21IS101)
-SHREYA S (1JS21IS102)
-SHREYAMBIKA GURUPRASADA HEGDE (1JS21IS103)
-SHUBODH S (1JS21IS104)