[BlueOnyx:15255] Re: Web Server Aliases for Sub Domains

[Michael Stauber]

Hi Tobias,

> The content for www.domain1.name shall be the same as for
> www.domain2.name (main site) and the content for
> ftp.domain1.name shall be the same as for ftp.domain2.name
> (a sub domain) - and so on.

Is the content for www.domain1.name the same as for ftp.domain1.name?

If so, then what I suggested will work very well.

If the content of www.domain1.name is different than that for
ftp.domain1.name, it'll work with a small modification.

If it is different, then I'd suggest to create a separate Vsite for
ftp.domain1.name and give it the web server alias of ftp.domain2.name.
Then untick the checkbox for "Web alias redirects" there as well.

Web server aliases work like this:

They are an additional FQDN that the site responds to when that URL is
accessed in a browser. The checkbox "Web alias redirects" just handles
what happens when someone accesses the alias:

Checkbox ticked: The visitor enters the FQDN of the alias in his
browser. The URL is accessed and redirects to the FQDN of the primary
name of the Vsite. The page loads and the URL in the browser shows the
primary FQDN of the site as it is named in the GUI.

Checkbox unticked: The visitor enters the FQDN of an alias in his
browser. The page loads and shows the contents of the /web folder of the
primary name of the site. BUT: The URL in the browser still shows the
URL of the alias. So for a visitor it appears that this is an
independent and separate site, but in reality it is not.

-- 
With best regards

Michael Stauber