On Sat, Jun 26, 2010 at 3:19 AM, Alvaro Lopez Ortega <[email protected]>wrote:
> On 25/06/2010, at 23:56, C. Mundi wrote: > > > I just set up a virtual server with the following parameters in the Basic > tab: > > Document Root = /srv/www/mydomain.net/public_html > > Directory Indexes = index.html > > > > and the following parameters in the Behavior tab: > > > > Directory / handled by List&Send with "alternate" Document Root = > /srv/www/mydomain.net/public.html/static > > > > And this setup works as expected when I place "index.html" in /static but > not when I put it in /public_html. > > Actually, the configuration does not make much sense because of a number of > reasons: > > - "Directory /" is the same thing as "Default". They match *all* requests. > Since there must be a default rule at the button of the rule list, odds are > you will not need a "Directory /" entry -- FTR: there are advanced/complex > cases where it'd be necessary though. > > - If you want your static content served from /, just set the document root > to the appropriate directory; in this case /srv/www/ > mydomain.net/public.html/static > > - Think of custom Document Root entries as exceptions. For instance: for > document root is /srv/www but you wanna have a web directory /icons point to > a path outside the document root, let's say /usr/share/icons/www. In this > case you'd add a rule "Directory /icons" with the custom document root (and > handler "Static content"). > > I think I understand. I was deliberately doing something a little unusual in an attempt to figure out the relationships without actually reading the code. I was not trying to suggest any that anything was counterintuitive, and I did not do a good job of making that clear. Thanks, cm
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
