Ok, thanks for mentioning RewriteLog, didn't know there is an extra logfile
for mod_rewrite. That helped me figuring it out:
In the second example, apache recognizes the rewritten url equals the
original url and aborts rewriting process. ("initial URL equal rewritten
URL: test/server.php [IGNORING
On 24/09/2010 4:36 PM, Walther Bauer wrote:
Yeah, I've unterstood that so far. But why does the second example _not_
produce an infinite loop?
You need to check the RewriteLog to find out why. It may depend on the context,
or other factors.
Frank
---
On Fri, Sep 24, 2010 at 4:36 PM, Walther Bauer <2313...@googlemail.com> wrote:
> Yeah, I've unterstood that so far. But why does the second example _not_
> produce an infinite loop?
Can you attach a rewritelog of the two cases? Must be some usually
uninteresting quirk as opposed to the standard l
Yeah, I've unterstood that so far. But why does the second example _not_
produce an infinite loop?
On 24/09/2010 9:59 AM, Walther Bauer wrote:
This .htaccess snippet creates an "Request exceeded the limit of 10 internal
redirects"-error on my server (XAMPP):
RewriteEngine On
RewriteRule ^(.*)$ ./server.php
while the following does not:
RewriteEngine On
RewriteRule ^(.*)$ server.php
So why
This .htaccess snippet creates an "Request exceeded the limit of 10 internal
redirects"-error on my server (XAMPP):
RewriteEngine On
RewriteRule ^(.*)$ ./server.php
while the following does not:
RewriteEngine On
RewriteRule ^(.*)$ server.php
So why does the "./" actually make a difference?
Than
