On Mon, Apr 21, 2008 at 10:47 AM, Hank <[EMAIL PROTECTED]> wrote:

>
> If the content is living on the same server as domainA.com (which it
> apparently is in this case), then you don't want to proxy. There is no
> need to create an additional HTTP request. You just instruct apache to
> grab the file directly. So you want something like
>
> >
> > RewriteCond  %{HTTP_HOST}   ^domainA.com$
> > RewriteRule   ^(.*)$  /home/user/public_html/siteA/$1
> >
> > If this doesn't work, tell us EXACTLY what happens: what do you see in
> > the browser, error_log, and access_log?
> >
>
>



I found part of the problem, but not how to solve it.

When configured as such:

RewriteCond  %{HTTP_HOST}   ^domainA.net$
RewriteRule   ^(.*)$  /home/user/public_html/siteA/$1 [L]


Apache is returning a 500 error.. the error_log shows:

"mod_rewrite: maximum number of internal redirects reached. Assuming
configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit
if neccessary."

I also found the httpd.conf on the server, and it doesn't seem to be doing
any other mod_rewrite stuff.

Why is it going into a recursive loop?

thanks.
-Hank

Reply via email to