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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.
--Josh Greenwood

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

>  #See if the requested page 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) implicitly forcing redirect (rc=302) with http://www.test.com/

Are you absolutely sure that the configuration quoted above is the
active one?  The RewriteLog says an implicit redirect is happening,
which strongly applies that the RewriteRule does not have the [P]
flag.  Try taking out all other RewriteRules temporarily, and make
absolutely sure you restart the server.

Joshua.


[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux