The following reply was made to PR mod_rewrite/2046; it has been noted by GNATS.
From: Will Vincent <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: mod_rewrite/2046: Rewrite Rule has different behavior form
1.2.1
Date: Wed, 08 Apr 1998 13:18:49 -0700
Hi,
I was able to figure it out thanks to your help. It
was definitely a configuration issue.
I was setting these in the Apache 1.2.5 server
ErrorDocument 401 /server/http-err-401.html
etc...
I needed to NOT redirect /server, for my rewrites
to work correctly.
Thanks much for your help, and sorry for wasting your time.
Will
At 06:52 AM 4/8/98 +0000, you wrote:
>[In order for any reply to be added to the PR database, ]
>[you need to include <[EMAIL PROTECTED]> in the Cc line ]
>[and leave the subject line UNCHANGED. This is not done]
>[automatically because of the potential for mail loops. ]
>
>
>Synopsis: Rewrite Rule has different behavior form 1.2.1
>
>State-Changed-From-To: open-feedback
>State-Changed-By: rse
>State-Changed-When: Tue Apr 7 23:52:53 PDT 1998
>State-Changed-Why:
>Although the correct ruleset would be
>
>RewriteEngine on
>RewriteCond %{REQUEST_URI} !^/protected-cgi-bin/foo\.cgi$
>RewriteCond %{REQUEST_URI} !^/protected-cgi-bin/foo2\.cgi$
>RewriteRule ^/(.*) http://www.server.com/$1 [L,R]
>
>(remember that the patterns are regex) I cannot
>reproduce your wrong behaviour. At least under 1.3b6-dev
>mod_rewrite evaluates the ruleset correctly. I got
>redirects for any URL except for the two listed
>CGI URLs. So, I expect that there are some other
>rulesets in your configuration which cause the wrong
>behaviour. Please double-check your configuration
>or at least enable RewriteLogLevel 9 and look
>what the RewriteConds actually evaluate.
>
