Hello Matthew, Yes, you do not need to use virtual servers for implementing that behavior. It is enough if you configure rules in the default virtual server.
Every single request will match it, independently of the targeted host. Then different rules will be applied depending on the concrete request. Basically, the host becomes an irrelevant parameter. You will have to add rules for resources like "Directory /wiki", "Directory /docs", etc. As far as I read on you original mail, it should be fairly straightforward to set them up. Good luck. -- Sent from my HTC ----- Reply message ----- From: "Matthew Haas" <[email protected]> To: <[email protected]> Subject: [Cherokee] Fathoming the impact of Rules, multiple Virtual Servers, one directory tree, and one host... Date: Wed, Jan 5, 2011 6:03 pm On 01/05/2011 10:57 AM, Alvaro Lopez Ortega wrote: >> So am I correct in perceiving Cherokee's "virtual servers" as >> administrative/functional domains for web processing (and not necessarily >> separate web domains-- but could be)? That's the impression I got from the >> docs. > Yes, that's it. A virtual server can hold more than a single domain. > Actually, it holds a number of web resources. How you match requests to that > virtual server is a completely different business. The most normal thing is > to check the host, although there are other types of matches: IP of origin, > protocol, etc. Is there information on the available types of matches? All I can seem to find/realize are hostname, IP, wildcard of hostname (regex of hostname)?... I don't see any mention of port (unless you mean the standard host:port nomenclature)... are there other ways? In my case, I'd specifically love to match based on the path in the URL... but what I seem to be reading here (and from my own experience testing cherokee) this doesn't appear to be working. > As I said, there are different matching mechanisms. It's up to you which to > use. The most common case is to use the wildcard matching (so you can > configure matches like: *.example.*), or regular expression matches (such us > .*\.example\.(com|org|net)), although there are others. > Okay, so with mentioning that stirs some of my original questioning... - Is it possible to have separate cherokee virtual servers that answer to the SAME domain name? For example: www.site.com And reachable from that site I want: www.site.com/docs/ and... www.site.com/wiki/ Both docs/ and wiki/ are under /var/www, but the processing I wish to be applied to either is quite different (regex for the wiki/, none (or a different set of regex) for docs/)... maybe php in one, or just index.html as an index in another? This is where I still find some confusion... from this most recent statement, it would seem I may not want to use virtual servers, because they may lack the ability to distinguish between the particular content I want to serve. So, reiterating my question: would virtual servers be what I'm looking for? Or am I looking at this the wrong way? Is it possible to do what I'm after in an elegant way through the cherokee admin interface? >> - Do rules receive JUST the "request" (path from docroot)? > Yes Ok, on second thought... maybe just an elaborate set of rules under one virtual server... perhaps playing with the custom document root... another avenue to explore at least. Thanks again, and sorry if I keep hammering with questions... as I said, I'm really liking cherokee, and am taking the time understanding it and hopefully get it to work. -Matthew _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
