"Namespace" cookie names to support subdomains.

My other thought is to restructure bakery to not care if a cookie from another domain is set, overwrite it if it needs one, ignore it if it doesn't.

In testing though, I can't seem to make that work, the cookie from the parent domain appears to win.

It seems parent domain cookies override sub domain cookies no matter what I do, so I went with namespace as the original proposal. Basically:

$type . md5($cookie_domain);

Resulting in:

CHOCOLATECHIP10b8124b78109b738f753a7c9962b1ae

D6 patch, D7 to follow.

Sorry, included another patch. Still rolling the 7.x patch.

7.x patch.

These patches also have add some DRY-ness to the SSL cookie patch.

I'm changing this to a bug, I'm sure it's not major, but it's pretty frustrating for our use case. Basically we can only have one Bakery environment on our domain without it (no demo, no dev-stage, etc).

I hear you, though I really think the complexity is minimal, considering the SSL patch that is already in. Here is the cookie name function from the patch:

 /**
<?php
/**
 * Generate the name for a bakery cookie, this prevents domain
 * mismatch on subdomains that are not part of a parent domains bakery config.
 *
 * @param string $type
 *   CHOCOLATECHIP or OATMEAL, default CHOCOLATECHIP
 * @return string
 *   The namespaced cookie name for this environment.
 */
function _bakery_cookie_name($type = 'CHOCOLATECHIP') {
  // Use different names for HTTPS and HTTP to prevent a cookie collision.
  if (ini_get('session.cookie_secure')) {
    $type .= 'SSL';
  }
  // Namespace the cookie by the cookie domain.  Use md5 to avoid using any
  // reserved cookie terms (all of which contain non-hex characters):
  //   "expires", "domain", "path", and "secure".
  $name = $type . md5(variable_get('bakery_domain', ''));
  return $name;
}
?>

I would love to see this patch go in or get some feedback - it's hard to roll other patches around it.

If the namespace is a show stopper, then maybe we can settle on using a function to name cookies and not smattering code everywhere that does it... that will make the namespace patch much smaller.

@BarisW - You probably have something in your VCL that is looking for SESS. Just add something similar to allow CHOCOLATECHIP.

If you need help, post your VCL somewhere and ping me in IRC.