Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id CAA08793; Fri, 1 Aug 1997 02:22:37 -0700 (PDT) Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by hyperreal.org (8.8.5/8.8.5) with SMTP id CAA08756 for ; Fri, 1 Aug 1997 02:22:28 -0700 (PDT) Received: from en by colin.muc.de with UUCP id <86103-2>; Fri, 1 Aug 1997 11:21:22 +0200 Received: by en1.engelschall.com (Sendmail 8.8.2) for new-httpd@apache.org id LAA11893; Fri, 1 Aug 1997 11:06:56 +0200 (MET DST) Message-Id: <199708010906.LAA11893@en1.engelschall.com> Subject: Re: [PATCH] more backref interpolation for rewriting engine To: new-httpd@apache.org (Apache Developer ML) Date: Fri, 1 Aug 1997 11:06:55 +0200 From: rse@engelschall.com (Ralf S. Engelschall) Organization: Engelschall, Germany. X-Home: http://www.engelschall.com/ X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org In article you wrote: > +1, but only if you change the name of mod_rewrite to mod_sendmail_cf. > just kidding. Yes, as everyone knows: Beside Larry Wall the guy named Eric Allman is my favorite hacker... And not just kidding: The header rewriting engine in Sendmail actually inspired mod_rewrites URL rewriting engine although I hated the ugly syntax of Sendmail rules. (I hope mod_rewrite's rules are a little bit better.. Hmmm..) > It is confusing for $N to back reference the url-pattern which appears > *AFTER* all the conditions. But other than that, sure why not. Yes, but this is the way since the early days. This has not changed. It is a little bit ugly in syntax when writing down the ruleset, but is _really essential_ for the rewriting engine to be performant. Because a rule can have as many conditions it likes and it would be horrible if the engine would first test all those conditions (regex compares!) and then match the pattern of the RewriteRule and just discover that the rule does not match. So, its a little bit confusing when reading rulesets but it is the best way we can program a rewriting engine so it has less overhead. > mod_rewrite programs are about as confusing as perl programs ;) Sure. mod_rewrite is such powerful because it has the same spirit built-in as Perl: Maximum flexibility. Or in other words (to adapt a statement from Perl for mod_rewrite): "mod_rewrite makes easy URL manipulations easy, and hard ones possible." Shouldn't we add this slogan to mod_rewrite.html? Another interesting point: Apache with mod_rewrite exists since Summer 1996 and is _STILL_ the only webserver which provides such a flexible engine for URL manipulations. So Apache is the only webserver which really can solve hard URL manipulation problems. Of course the same applies to other nice things of Apache. But I love to think about these facts and I love to know that we beat all the others. The mod_rewrite user reponses over the last year showed that although mod_rewrite is complicated the real webmaster needs such a functionality. Greetings, Ralf S. Engelschall rse@engelschall.com www.engelschall.com