I haven't used Cherokee for a while, but this is known as a rewrite rule
("internal" redirect).On Wed, May 1, 2013 at 8:27 PM, Anfré Littoz <[email protected]>wrote: > Hi, > > Don't know if this the proper place for such a question, so excuse me if > this is considered as "noise". > > I'm presently testing Cherokee as an alternative to Apache for the LXR > project (see http://lxr.sourceforge.net). As long as I use elementary LXR > configuration features, it works fine. > > But, when I come to try to serve several databases (for short, database is > the closest ordinary concept equivalent to its "service") with a single > application instance, a trick is played on the URI, which I can't fancy how > to convert. > > LXR is driver by this kind of URI: > > http://hostname/LXR_service_signature/DB_id > /script_file/path_for_script?arguments > > i.e. an argument-like is interspersed inside the web-path for the script. > Under Apache, directive AliasMatch strips off this information and > simultaneously routes the request to an alternate document root. The > important point is the original URI is not changed and available for > parsing unaltered by the script which retrieves the DB_id. > > In my conversion attempt, I used either a directory rule (on > LXR_service_signature) or regexp rule, both with a redirect handler to > remove the DB_id and other non-path related bits. Unhappily, this rewrites > the URI and defeats the script processing which no longer can retrieve the > DB_id. > > Does there exist in Cherokee a means to launch a script whose command line > is generated from groups ($1, $2, ...) captured by the regexp-based rule so > that the URI is unaltered (environment variables reflect the initial URI)? > > ajl > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
