Timeline for Is it acceptable for user agents to modify cookies other than by instruction from the server?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2016 at 10:26 | vote | accept | Robert | ||
| Feb 17, 2016 at 10:26 | comment | added | Robert | Yes, this may be better in another thread. I was looking for examples where the client would want to set the state not the server. If the client was using the cookies just as storage it would be better off storing it in local storage. Your answer is useful so I am just going to accept. | |
| Feb 17, 2016 at 4:48 | comment | added | user176267 | @Robert This might be suited to a new thread, but I'll continue anyway. Once a cookie is set it is persistent until it expires. One example: the server stores associated data (e.g. login user) with a session cookie, which is a unique identifier. I can't think of a simpler way to keep someone logged in. Here's Google's cookie policy. What do you mean by doing it separately? | |
| Feb 16, 2016 at 11:01 | comment | added | Robert | Ok I guess a better question might be why you would want to do it? If it is to store state it's better doing it separately since it makes the requests larger. If it's to send data to the server, it is better using other headers that the server can't modify itself? | |
| Feb 15, 2016 at 21:59 | history | edited | user176267 | CC BY-SA 3.0 |
added 518 characters in body
|
| Feb 15, 2016 at 21:12 | review | First posts | |||
| Feb 18, 2016 at 22:44 | |||||
| Feb 15, 2016 at 21:09 | history | answered | user176267 | CC BY-SA 3.0 |