Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When we use an auto sub domain: demo.domain.com
The sites spin up and we can access them fine.
However, when you try to login to the site via the auto sub domain alias such as:
www-site-com.demo.domain.com
You get access denied and refreshed back to the login screen. If you set the cookie_domain in local.settings.php it all works as expected:
$cookie_domain = 'www-site-com.demo.domain.com';
Is this by design?
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedThere was some confusion because of issues with Domain Access used in different modes - logging in via any alias keeps you logged out on another alias then, so it is required to use
SERVER_NAME
instead ofHTTP_HOST
, but because we can't determine if DA is enabled and how this module is used, we have switched to useHTTP_HOST
for$cookie_domain
by default, as it was previously.See the code for reference: http://drupalcode.org/project/octopus.git/blob/HEAD:/aegir/conf/global.i...
Note that you can still force using
SERVER_NAME
for$cookie_domain
with control filemodules/cookie_domain.info
Comment #2
snlnz CreditAttribution: snlnz commentedmakes sense. Thanks for the reply.