>> 
>> While a "SiteRoot" can be mapped by 2 or more domains, it isn't
>> possible to map 2 "SiteRoots" to one domain, or use the same
>> "SiteRoot" in multiple sites.
>> 
>> This is also because, when accessing magnolia without the domain (eg
>> "localhost" or by IP), the "SiteRoot" must be used to disambiguate the
>> desired Site (Unshortened URL).
> 
> Yes, that what you say is true.
> Magnolia couldn't guess which site configuration to use when accessing
> the website as 'localhost' or by IP.
> 
> But what about the case when I do access the website with 
> the correct domains (those defined in the site configuration).
> Is there any reason why it shouldn't work in this situation?

If you access the server with the correct domain, then yes, you should get the 
correct site resolved. BEWARE that you will most likely need to add mappings 
also for all the other workspaces (resource, dms, ...) used by your content.
Also all the links would need to be relative ... which might be a bit of an 
issue. You might have to write your own link resolver since it is possible that 
in this case Magnolia will choose to resolve links as absolute to ensure links 
point to what it thinks is a correct target domain.
Cache should be ok, since it contains the server name in the key.

Jan

> 
>> Regards from Vienna,
>> 
>> Richie
> 
> Thanks and regards,
> Bobi.
> --
> Go mobile with Netcetera - http://netcetera.ch
> 
> Bozidar Ilievski | [email protected]
> T +389 -2- 306 45 32 | F +389 -2- 307 94 95
> Netcetera DOO | 1000 Skopje | Macedonia | http://netcetera.com.mk
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to