Hmm I thought rewrite rules shouldn't change the URI if they're marked as "internal". Does LXR have instructions for Nginx or Lighttpd? If so, you should be able to convert those rules to Cherokee rules. Apache has so many configuration options that sometimes it's hard to find the exact match.
On Wed, May 1, 2013 at 10:57 PM, Anfré Littoz <[email protected]>wrote: > Yes, this is a rewrite rule and consequently it changes the URI. > > What I need is a rule, which can be flagged "final", causing execution of > a CGI script whose home directory is known (e;g. /cgi-bin) and whose name > and eventually arguments are taken from the URI ($x substitutions) while > the environment variables SERVER_NAME, SCRIPT_NAME, ... are set from the > original URI. > > From the documentation, I'm afraid this is not possible with Cherokee. > > The alternate solution would be to remove DB_id from the "script web path" > part since this was a bad design decision as it mixes script path and > argument but this involves a major rewrite of LXR initialisation and > configuration. Maybe this is the wise direction since it could greatly > simplify integration with web servers and allow for more server candidates. > > ajl > > ------------------------------ > *De :* Daniel Lo Nigro <[email protected]> > *À :* cherokee List <[email protected]> > *Envoyé le :* Mercredi 1 mai 2013 14h33 > *Objet :* Re: [Cherokee] Migration from Apache to Cherokee: URI tweaking > > I haven't used Cherokee for a while, but this is known as a rewrite rule > ("internal" redirect). > > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > > > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > >
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
