Prior to the ability to use mappings individually with vhosts, a global
mapping was common among all hosts, right?
So if a global mapping such as
[aliases]
/images/ = D:/Photoshop/images/museums/
was used,
http://www.vhost1.com/images/ = http://www.vhost2.net/images/
-Jeff
At 08:20 PM 06/10/2004, Peter wrote:
Anything on host1 should NOT be viewable of host2 in a normal vhost setup
with 2 hosts. It is automatically accomplished. Only if the sounds and
images are not in the web root will they need to be mapped and you can map
them globally or by vhost.
http://www.vhost1.com/images/ != http://www.vhost2.net/images/
http://www.vhost1.com/sounds/ != http://www.vhost2.net/sounds/
Now I give up.
-----Original Message-----
From: <[EMAIL PROTECTED]>
To: "sambar List Member" <[EMAIL PROTECTED]>
Date: Fri, 11 Jun 2004 00:31:28 +0200
Subject: [sambar] Different mappings for different virtual hosts
> Jeff,
>
> Thanks for your mail. What you wrote is what I would like to
> accomplish.
> >http://www.vhost1.com/images/ != http://www.vhost2.net/images/
> >http://www.vhost1.com/sounds/ != http://www.vhost2.net/sounds/
> This is exactly what I would like to avoid, that 'FolderA' can be
> accessed
> via domainA AND domainB. And now this is possible because the alias
> folders you assign in your mappings.ini can NOT necessarily be accessed
> via all vhosts you create. This separation makes lot of sense to me.
>
> Thanks to all for your help and mails.
>
> Rgds,
> Marcus
-------------------------------------------------------
To unsubscribe please go to http://www.sambar.ch/list/
