Right now, Rails sets a session cookie with the name _wellcomelibrary_alpha on every page load (with a random value). This is useful when people sign in, as it means they can stay signed in – but when logged out I'm not sure it does much (as we don't have any basket / personalisation features for signed out users).
Removing the cookie for signed out users might be beneficial, as we've set CloudFront up to cache the responses from the Origin server based on cookies – so at the moment, it can't share the cache for any of the HTML pages between users, whereas if we remove it, those pages become cacheable again.
frankieroberto
commented
8 years ago
Right now, Rails sets a session cookie with the name
_wellcomelibrary_alphaon every page load (with a random value). This is useful when people sign in, as it means they can stay signed in – but when logged out I'm not sure it does much (as we don't have any basket / personalisation features for signed out users).Removing the cookie for signed out users might be beneficial, as we've set CloudFront up to cache the responses from the Origin server based on cookies – so at the moment, it can't share the cache for any of the HTML pages between users, whereas if we remove it, those pages become cacheable again.