I have a Rails app that is storing some user information in a cookie, and that information isn’t being stored as soon as I would like. A client that is performing five requests in a row from a single page has an empty cookie until the page has completely loaded, and then for the future, the cookie is populated. It is behaving as if the client doesn’t actually commit the cookies until the page is loaded. This is true using multiple browsers, so it doesn’t appear to be purely a quirk of any one particular browser. Is there any way to commit those, or am I going to have to find another workaround?
Share
Could you explain in more detail what you’re doing to generate five rails requests in the context of a single page load? Can you guarantee the order in which these requests will arrive at the web server?
I’m guessing that cookies aren’t going to be the optimal way of accomplishing what you’re trying to do.