Re: [users@httpd] rewriterule causing [redirect/302] error

[Josh Greenwood <joshgreenwood@xxxxxxxxx>]

Here is the rewritecond with the corresponding rewritelog:

# See if the input URL is http://www.test.com
RewriteCond  %{SERVER_NAME}  www.test.com
# It is. Now see if www.test.com is a folder in the webcontent/ directory
RewriteCond  %{DOCUMENT_ROOT}/webcontent/%{SERVER_NAME} -d
# it is. 
RewriteRule  ^/(.*)$ http://%{SERVER_NAME}%{REQUEST_URI} [P,L]

(2) init rewrite engine with requested uri /
(3) applying pattern '^/(.*)$' to uri '/'
(4) RewriteCond: input='www.test.com' pattern='www.test.com' => matched
(4) RewriteCond: input='E:/egranary/webcontent/www.test.com' pattern='-d' => matched
(2) rewrite / -> http://www.test.com/
(2) forcing proxy-throughput with http://www.test.com/
(1) go-ahead with proxy request proxy:http://www.test.com/ [OK]

It is bringing up the local page instead of the web version.
-Josh Greenwood

On 10/5/05, Joshua Slive <jslive@xxxxxxxxx> wrote:

On 10/5/05, Josh Greenwood <joshgreenwood@xxxxxxxxx> wrote:
> No, the quoted rewritelog is the result of the [P] flag not being there. The
> problem is when the [P] flag is there, it
>  grabs the page out of the local 'webcontent' folder instead of getting the
> Internet version.

Then show the RewriteLog with the P flag.  There is no point analyzing
an obviously wrong configuration.

Joshua.