Cookies can be stripped by reverse proxy caches and not passed on to Drupal. In our case, we're using Pantheon which doesn't pass the cookie the first time round which means we can't access the same temp storage.

Pantheon provides naming conventions for avoiding this issue.

Would it cause problems elsewhere if the cookie was renamed to SESSstoreid?

CommentFileSizeAuthor
#4 rename_cookie_to_bypass_cache-3129813-4.patch1.75 KBimclean
#2 rename_cookie_to_bypass_cache-3129813-2.patch1.54 KBimclean

Comments

imclean created an issue. See original summary.

imclean’s picture

imclean commented
Status: Active » Needs review
StatusFileSize
new rename_cookie_to_bypass_cache-3129813-2.patch1.54 KB
nortmas’s picture

nortmas commented

Hi, no, I don't think it can cause errors as long as the patch is correct. I've run tests. Let's see.

imclean’s picture

imclean commented
StatusFileSize
new rename_cookie_to_bypass_cache-3129813-4.patch1.75 KB

Updated comments and notifications.

  • nortmas committed 025bb4a on 8.x-1.x 
    Fixes for the issues: #3129813, #3148746,
nortmas’s picture

nortmas commented
Version: 8.x-1.x-dev » 8.x-1.0
Assigned: Unassigned » nortmas
Status: Needs review » Fixed

Hi @imclean, I've released a new version (8.x-1.1) of the module, where you can override the cookie name to conform to the required policy.
To change the default cookie name you need to add the next lines to your .services.yml file:

parameters:
  session_based_temp_store.cookie_name: 'SESSstoreid'

I didn't hard code it with yours because the other users may use the default cookie name in the existing projects so it may break their existing user's sessions.

And I close this task.

nortmas’s picture

nortmas commented
Status: Fixed » Closed (fixed)