Replace/Append Cookies
When we assign a new cookie value to document.cookie, the current cookie is not replaced. The new cookie is parsed and its name-value pair is appended to the list. The exception is when you assign a new cookie with the same name (and same domain and path, if they exist) as a cookie that already exists. In this case, the old value is replaced with the new.
Reading Cookie
We can read cookies by a document.cookie. The problem occurs when we need the specific part of the cookie to perform some action.
Deleting Cookies
A cookie is deleted by setting a cookie with the same name (and domain and path, if they were set) with an expiration date in the past and if using max-age then must set a negative value.
Ex: –
Updating Cookies
A cookie is possible to update by setting a new value to a cookie with the same name.
Cookies Security Issues
- Can misuse Client Details
- Can track User
- Client Can Delete Cookies
- Client can Manipulate Cookies
Cookies Limitation
- Support HTML4 / HTML 5
- Each cookie can contain 4kb Data
- Cookies can be stored in Browser and server
- It is sent with each request
