-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any need to add $cookie_domain to settings.php file? #40
Comments
If the |
Now that issue #39 is fixed it leaves me wondering what other benefits having the `$cookie_domain = '.example.com'; may have. |
This is related to issue #32. |
@izmeez - I tested this: So whether do you or not might depend on use case and whether the same users have access on all domains:
I think the comment in /**
* Backdrop automatically generates a unique session cookie name for each site
* based on its full domain name. If you have multiple domains pointing at the
* same Backdrop site, you can either redirect them all to a single domain (see
* comment in .htaccess), or uncomment the line below and specify their shared
* base domain. Doing so assures that users remain logged in as they cross
* between your various domains. Make sure to always start the $cookie_domain
* with a leading dot, as per RFC 2109.
*/
// $cookie_domain = '.example.com'; |
@yorkshire-pudding Thanks for pointing that out. I had overlooked it being in the settings.php file by default. I am inclined to consider adding a reference to it in the domain install quickstart. |
Is there any need to add a $cookie_domain line in the settings.php file?
$cookie_domain = '.example.com';
As suggested in the old comment, https://www.drupal.org/project/domain/issues/1559486#comment-10176824
The text was updated successfully, but these errors were encountered: