Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So the situation is that on a given page there are many HTTP requests and each of these need to update a single shared cookie. There is no possibility to control how many requests are made per page, but realistically there can be 10+.
We’ve seen issues where only the last http request successfully updates the cookie and I am told this is due to browser dependencies.
Is this a known issue in general and are there any strategies for mitigating the risk?
One strategy is to avoid storing mutable information in the cookie itself, and instead have the cookie be an identifier of some sort that identifies a record in a database of some kind somewhere. Then, your server updates information in the (server-side) database, instead of changing the cookie value.