May cookie_domain a problem for a (virtual) site instance? [#1507888]

What it cannot do
For the following settings you'd still need Drupal's multi-site feature:
PHP configuration and cookie_domain.

What does cookie_domain mean? The cookie only valid for the address in browser? Or could it a problem for a "multisite" with more than one domains? Could it be a session/ login problem for virtual sites?

Comments

Comment #1

djg_tram CreditAttribution: djg_tram commented 30 March 2012 at 09:16

Cookie_domain is a setting in sites/default/settings.php. Normally, unique session cookie names are generated for the full domain name, meaning that if you have closely related sites like www.example.com and subdomain.example.com, users logging into one cannot cross to the other without a separate login. If you specify cookie_domain to be "example.com", login authentication will use the "example.com" part only, meaning that users can freely move between the subsites. This is something VS can't provide.

Comment #2

JohnnyX CreditAttribution: JohnnyX commented 30 March 2012 at 09:29

Ok. I try to build "subsites" which use a (complete) own domain name. Should it work or could be a problem?

At the moment a take a look at og/ virtualsites. I know domain_access but would prefer a simple og/ virtualsite solution. Each virtual site should shown as a "full website", but internal it handled only as a group...

Comment #3

djg_tram CreditAttribution: djg_tram commented 30 March 2012 at 10:16

Wait a minute. :-))

I just copied the description automatically from settings.php and the older description of VS but now that I really think about it, I do have websites where VS and cookie_domain work together without the slightest problem. I don't think there is any problem with those two, or if there is, I'm afraid I don't know what was meant with this remark.

In the particular case I checked, I have both www.example.com and m.example.com for normal and mobile visitors. The website is actually the same, VS only switches the theme depending on the subsite. It works with cookie_domain all right, you can move across the sites with the same login.