Well, quite frankly, you’re mistaken. We run on Siteground’s VPS servers. We disabled dynamic cache. We disabled memcached. We disabled browser caching in dev mode. THEN, we pulled out a brand new machine, on a brand new browser installation, in incognito mode, and guess what…? The server delivered the cookied-version of the webpage to that browser that was cached from a completely different session.
The ONLY way we were able to get this behavior to stop for unauthenticated users was to use the code we provided above.
You can dismiss it as any type of error you want, but the truth is that the directive is preventing cookies from personalizing the user experience for users that aren’t authenticated.
Edit: I’d also like to add that (after making the requested modifications) we were able to re-activate dynamic caching and everything seems to play nice again. For what it’s worth, the cookie in question is being set via Ajax… not sure if that matters.
-
This reply was modified 5 years, 2 months ago by phvntom. Reason: Additional information
