In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

View Revisions: Issue #95		[ All Revisions ] [ Back to Issue ]
Summary	0000095: Support for Multi-Domain Installation

Revision	2009-06-18 15:46:09 by alex
Description	In order to fully support multi-domain installation we need to rework and improve cookie domain detection. Currently $_SERVER['HTTP_HOST'] is used as cookie domain, however there are cases when you can't fully rely on this especially in cases with single installation running on multiple Domains. Example: demo.in-portal.net, demo.in-portal.com, www.in-portal.org, in-portal.org Proposing: a. Add new configuration variable: CustomCookieDomains where administrator can list all domain names (one per line) on which In-Portal matches domain from $_SERVER['HTTP_HOST']. User must enter exact cookie domain (with all leading dots if any). b. New variable will be placed in Admin->Configuration->Website->Advanced: Cookie Settings section and will be disabled/empty by default so it works as they are now. When - nothing is entered into CustomCookieDomains variable - when none of entered cookie domains will match domain from $_SERVER['HTTP_HOST'] and $_SERVER['HTTP_HOST'] consists of 3 parts (e.g. "www.domain.com" or "ftp.domain.com"), then we automatically detect cookie domain as ".domain.com" (last 2 parts). In case, when $_SERVER['HTTP_HOST'] consists of more, then 3 parts, then use $_SERVER['HTTP_HOST'] as cookie domain. When cookie domains from configuration variable are matched, then leading dot should be stripped (only when matching). domain.com sub.domain.com www.domain.com will match to "domain.com"

Revision	2009-06-18 15:30:00 by alex
Description	In order to fully support multi-domain installation we need to rework and improve cookie domain detection. Currently $_SERVER['HTTP_HOST'] is used as cookie domain, however there are cases when you can't fully rely on this especially in cases with single installation running on multiple Domains. Example: demo.in-portal.net, demo.in-portal.com, www.in-portal.org, in-portal.org Proposing: a. Add new configuration variable: CustomCookieDomains where administrator can list all domain names (one per line) on which In-Portal matches domain from $_SERVER['HTTP_HOST']. User must enter exact cookie domain (with all leading dots if any). b. New variable will be placed in Admin->Configuration->Website->Advanced: Cookie Settings section and will be disabled/empty by default so it works as they are now. When - nothing is entered into CustomCookieDomains variable - when none of entered cookie domains will match domain from $_SERVER['HTTP_HOST'] and $_SERVER['HTTP_HOST'] consists of 3 parts (e.g. "www.domain.com" or "ftp.domain.com"), then we automatically detect cookie domain as ".domain.com" (last 2 parts). In case, when $_SERVER['HTTP_HOST'] consists of more, then 3 parts, then use $_SERVER['HTTP_HOST'] as cookie domain.

Revision	2009-06-18 15:03:57 by alex
Description	In order to fully support multi-domain installation we need to rework and improve cookie domain detection. Currently $_SERVER['HTTP_HOST'] is used as cookie domain, however there are cases when you can't fully rely on this especially in cases with single installation running on multiple Domains. Example: demo.in-portal.net, demo.in-portal.com, www.in-portal.org, in-portal.org Proposing: a. Add new configuration variable: CustomCookieDomains where administrator can list all domain names (one per line) on which In-Portal matches domain from $_SERVER['HTTP_HOST']. b. New variable will be placed in Admin->Configuration->Website->Advanced: Cookie Settings section and will be disabled/empty by default so it works as they are now. When nothing is entered into CustomCookieDomains variable, then all will work as before. Same, when none of entered cookie domains will match domain from $_SERVER['HTTP_HOST']. Additionally after clean installation in case, when $_SERVER['HTTP_HOST'] consists of 3 parts (e.g. "www.domain.com" or "ftp.domain.com") we can set mentioned above configuration variable to ".domain.com" or "domain.com".

Revision	2009-06-18 15:03:17 by alex
Description	In order to fully support multi-domain installation we need to rework and improve the following components and mechanisms: 1. Cookies. Currently $_SERVER['HTTP_HOST'] is used as cookie domain, however there are cases when you can't fully rely on this especially in cases with single installation running on multiple Domains. Example: demo.in-portal.net, demo.in-portal.com, www.in-portal.org, in-portal.org Proposing: a. Add new configuration variable: CustomCookieDomains where administrator can list all domain names (one per line) on which In-Portal matches domain from $_SERVER['HTTP_HOST']. b. New variable will be placed in Admin->Configuration->Website->Advanced: Cookie Settings section and will be disabled/empty by default so it works as they are now. When nothing is entered into CustomCookieDomains variable, then all will work as before. Same, when none of entered cookie domains will match domain from $_SERVER['HTTP_HOST']. Additionally after clean installation in case, when $_SERVER['HTTP_HOST'] consists of 3 parts (e.g. "www.domain.com" or "ftp.domain.com") we can set mentioned above configuration variable to ".domain.com" or "domain.com".

Revision	2009-06-18 14:43:59 by alex
Description	In order to fully support multi-domain installation of In-Portal we need to rework and improve the following components and mechanisms: 1. Cookies. Currently domain name for Cookie is auto-detected from Webserver variables, however there are cases when uoi can't fully rely on this especially in cases with single installation running on multiple Domains. Example: demo.in-portal.net .demo.in-portal.com .in-portal.org Proposing: a. Add 2 new config vars. - UseCustomCookieDomains (check-box) and CustomCookieDomains where admin can list all domain names (one per line) on which In-Portal matches loaded domain. b. New variable will be placed in Admin->Configuration->Website->Advanced: Cookie Settings section and will be disabled/empty by default so it works as they are now 2. Redirects NON-SSL <=> SSL ANy proposals with this?

Web Development by Intechnic

In-Portal Open Source CMS